Filter
Top Products
5.3 Linux Support 21
the comp onents may take a while, it is often useful to perform this
step by itself after configuration.
The get makefile target can be used to perform this step.
Note that the original web locations are generally used for each library
supported by the userland build. This is generally a good thing, but
also means that things sometimes move.
We try to keep a set of archives on the Boundary Devices website for
use when the original sources are unavailable.
Look here if you can’t find something.
3. Build libraries under build/ the system through the kconf tool.
As mentioned earlier, the build tool allows you to express inter-library
dependencies in their makefile packets.
The packets for each component are stored in userland/rules and
consist of both a configuration piece *.in and build instructions *.make.
The install target can be used to simply build the components with-
out making a root filesystem.
4. Install libraries into install/. This mingling of various libraries is
done to allow simplified include file and library references for depen-
dent packets.
5. Build a root filesystem under root/. This step gathers all of
the executable portions (applications and shared libraries) for each
component into a root filesystem image. Scripts are also commonly
installed, as are any supporting configuration files (under root/etc).
The rootfs target can b e used to create the root filesystem without
creating a flattened image.
6. Build a device table. This step uses the kernel configuration file to
create devices.txt, suitable for use with genext2fs, mkcramfs, or
mkfs.jffs2.
The devices target can be used to create the device table without
performing any other build steps.
7. Flatten the root filesystem into any of cramfs, initrd, or JFFS2
images for placement in flash or SD card.
December 28, 2005 Revision 2.8