NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

documentation: insist more on why output/target/ should not be used

Browse Source 
A lot of people complain that the root filesystem generated by
Buildroot doesn't work because it lacks the device files. This is
because they use output/target/ instead of one of the images.

Therefore, insist in the documentation on this point. Even though I'm
unsure if users really read the documentation :-)

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Thomas Petazzoni 2009-10-30 09:06:47 +01:00
parent 83f1ec65a0
commit 5e5f3209f0
1 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/buildroot.html
View File

@ -207,13 +207,19 @@
binaries and libraries, that make it far too big for an embedded binaries and libraries, that make it far too big for an embedded
system.</li> system.</li>
<li><code>target/<code> which contains the root filesystem for <li><code>target/</code> which contains <i>almost</i> the root
the target. Only the necessary files to run the libraries and filesystem for the target: everything needed is present except
applications are installed in this directory. However, the device files in <code>/dev/</code> (Buildroot can't create
<code>target/dev/</code> doesn't contain the device files, as them because Buildroot doesn't run as root and does not want to
creating device files requires the root access. The device files run as root). Therefore, this directory <b>should not be used on
only exist in the root filesystem image produced by your target</b> but instead you should use one of the images
Buildroot.</li> built in the <code>images/</code> directory. If you need an
extracted image of the root filesystem, for booting over NFS,
then use the tarball image generated in <code>images/</code> and
extract it as root.<br/>Compared to <code>staging/</code>,
<code>target/</code> contains only the necessary files to run
the libraries and applications: all the development files
(headers, etc.) are not present.</li>
<li><code>host/</code> contains the installation of tools <li><code>host/</code> contains the installation of tools
compiled for the host that are needed for the proper execution compiled for the host that are needed for the proper execution