Classic Setting Up Build Environment
Create a new directory for the build environment:
|Create the directory|
$ mkdir $HOME/oe $ cd $HOME/oe
To be able to download sources from the net, it may be required to configure Proxy Settings.
Now check out the following repositories:
|Clone Arago repositories|
$ git clone git://arago-project.org/git/arago.git $ git clone git://arago-project.org/git/arago-oe-dev.git $ git clone git://arago-project.org/git/arago-bitbake.git
Replace "git" protocol with "http" or "ssh", depending on the required access.
Note: If you know what you are doing, you can try using Arago overlay with upstream OpenEmbedded and BitBake repositories.
The directory should now be populated with 3 subdirectories –
arago/setenv file and make sure environment variables are set properly.
OEBASE should point to the directory you’ve created in the beginning:
Also, in order to use a separate "scratch" area outside of home directory, you may want to enable
SCRATCH variable and point it appropriately:
Now, source this file to set the environment variables:
$ . arago/setenv
Or alternatively (which is the same, but maybe required if using other shell than bash):
$ source arago/setenv
TI Note: Users of TI RHEL4 systems should also source the
arago/ti-rhel4-setenv to set additional paths:
$ . arago/ti-rhel4-setenv
If not done before, set the
PATH variable to point to the CodeSourcery toolchain (refer to Getting CodeSourcery Toolchain for obtaining one):
$ export PATH=/opt/arm-2007q3/bin:$PATH
arago-csl-sdk.tar.bz2 from http://arago-project.org/files/short-term/extras/ on top of the CodeSourcery toolchain (that may require root permissions, depending where CS toolchain was installed):
# tar -jxvf arago-sdk-bins/arago-csl-sdk.tar.bz2 -C /opt/arm-2007q3
Now it should be ready to start a build of the minimal filesystem image:
$ bitbake arago-base-image
Or to build a bigger filesystem with more applications, libraries and tools:
$ bitbake arago-demo-image
To build a kernel, use the following command. Please note, that currently only PSP and linux-omap linux kernels for OMAP3 EVM and linux-omap kernel for BeagleBoard are supported. DaVinci platforms use linux-davinci kernels and also can use linux-davinci-staging, which is a staging area for upcoming features.
$ MACHINE=omap3evm bitbake virtual/kernel $ MACHINE=beagleboard bitbake virtual/kernel $ MACHINE=dm6446-evm bitbake virtual/kernel $ MACHINE=dm355-evm bitbake virtual/kernel
Resulting images and packages will be placed under
arago-deploy directory -
images for the filesystem, kernel and bootloader; and
ipk for binary IPK packages, respectively.