jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 14:16:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

documentation: Mention the fact that the skeleton location can be configured

Browse Source 
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Thomas Petazzoni 2010-11-24 13:20:09 +01:00
parent 3aac10520a
commit 49b3ac6560
1 changed files with 8 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/buildroot.html
View File

@ -335,19 +335,14 @@
completely rebuild your toolchain and tools, these changes will be completely rebuild your toolchain and tools, these changes will be
lost.</li> lost.</li>
<li>Customize the target filesystem skeleton available under <code> <li>Create your own <i>target skeleton</i>. You can start with
fs/skeleton/</code>. You can customize configuration files or other the default skeleton available under <code>fs/skeleton</code>
stuff here. However, the full file hierarchy is not yet present and then customize it to suit your
because it's created during the compilation process. Therefore, you needs. The <code>BR2_ROOTFS_SKELETON_CUSTOM</code>
can't do everything on this target filesystem skeleton, but changes to and <code>BR2_ROOTFS_SKELETON_CUSTOM_PATH</code> will allow you
it do remain even if you completely rebuild the cross-compilation to specify the location of your custom skeleton. At build time,
toolchain and the tools. <br /> You can also customize the <code> the contents of the skeleton are copied to output/target before
target/generic/device_table.txt</code> file, which is used by the any package installation.</li>
tools that generate the target filesystem image to properly set
permissions and create device nodes.<br /> These customizations are
deployed into <code>output/target/</code> just before the actual image
is made. Simply rebuilding the image by running make should propagate
any new changes to the image.</li>
<li>Add support for your own target in Buildroot, so that you <li>Add support for your own target in Buildroot, so that you
have your own target skeleton (see <a href="#board_support">this have your own target skeleton (see <a href="#board_support">this