-
Notifications
You must be signed in to change notification settings - Fork 35
Building the SDK
This page acts as a short guide on how to build the SDK using the provided build scripts.
Please note: Your source directory, build and work directories must not have spaces in their names. This is due to a limitation of the GNU Autotools.
Before building the SDK, please make sure you have the required prerequisites installed. These are listed separately for [Linux](Building on Linux), [Windows](Building on Windows) and [OS X](Building on Mac).
mkdir buildroot && cd buildroot
git clone --branch 2014.11 https://github.com/adapteva/epiphany-sdk.git sdk
./sdk/build-epiphany-sdk.sh -C a armv7l -c arm-linux-gnueabihf-
You might need to adjust arm-linux-gnueabihf- to match your cross compiler. Please notice the trailing dash.
./sdk/build-epiphany-sdk.sh -C -a x86_64
./sdk/build-epiphany-sdk.sh -C -a armv7l
Building on the Parallella is slow and can take several hours. This depends a lot on your uSD-card.
Firstly, the source code of the SDK must be downloaded, as demonstrated in Downloading the SDK.
To simplify things you should store the directory into which you downloaded the sources in a variable.
export EPIPHANY_BUILD_HOME="/path/to/download_directory"
Where '/path/to/download_directory' is the absolute path to the directory containing the downloaded SDK tree.
To build the SDK use the build-epiphany-sdk.sh script.
cd $EPIPHANY_BUILD_HOME
sdk/build-epiphany-sdk.sh
Once begun, a successful build will end with the following message:
**************************************************
The build is complete.
The tools have been installed at: /usr/local/bin
Please ensure that this directory is in your PATH.
**************************************************
export PATH=${EPIPHANY_BUILD_HOME}/esdk.5.13.09.10/tools/e-gnu/bin/:$PATH
After this, typing epiphany-elf-gcc --version or e-gcc --version should run Epiphany GCC and dump the version information.
If the build has failed, the build log should be checked to see what has caused the error. Usually this is due to a prerequisite package not being installed, so please re-check that you have all the prerequisites installed (please visit the relevant page for your Operating System, Linux, Windows and OS X, for more information). If needed, the SDK forums should be used for support and a bug submitted.