3,260
edits
Changes
m
→Adding platform specific components not provided with Buildroot
{{InfoBoxTop}}
{{Applies To Linux}}
{{AppliesToNaonAppliesToNaonFamily}}{{Applies To Diva}}
{{InfoBoxBottom}}
[[File: Buildroot-arch.jpg|600px]]
== Configure the build options ==
From the ''Build options'' menù you can define some custom directories for compilation output and file download. It is also recommended to enable the compiler cache and optionally set a custom directory.
[[File: Buildroot-options.jpg|600px]]
== Setting up the external toolchain ==
* Toolchain -> Toolchain path (eg. /home/shared/devel/dave/naon-DAA/sw/linux/sdk/arm-2009q1)
* Toolchain -> Toolchain prefix (eg. $(ARCH)-none-linux-gnueabi)
* Toolchain -> External toolchain C library -> Select glibc/eglibc
* Toolchain -> Activate RPC support
* Toolchain -> Activate C++ support
[[File: Buildroot-toolchain.jpg|600px]]
The list of available packages can be accessed entering the '''Package selection for the target''' option
It's important that busybox provides the '''depmod''' command, which is not enabled by default. To enable it, you need to modify the buildroot/package/busybox/busybox-1.20.x.config file adding
<pre>
CONFIG_DEPMOD=y
CONFIG_DEFAULT_DEPMOD_FILE="modules.dep"
</pre>
= Building the root file system =
</pre>
to start the build process(the "O=" parameter is optional), which will perform the following tasks:
* download source files (as required);
= Adding platform specific components not provided with Buildroot =
The targets usually provides specific features that relies on software components which can't be provided by the standard Buildroot project. Adding these components to the Buildroot root file system usually requires further operations, which depends on the particular target. The following sections provide instructions on how to perform these operations on '''DAVEEmbedded Systems'''s targetsSOMs.
== Adding Naon/Maya specific components==