From 49b3ac65607d855889671b27cd6b9f6c1e4f6417 Mon Sep 17 00:00:00 2001 From: Thomas Petazzoni Date: Wed, 24 Nov 2010 13:20:09 +0100 Subject: [PATCH] documentation: Mention the fact that the skeleton location can be configured Signed-off-by: Thomas Petazzoni --- docs/buildroot.html | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/docs/buildroot.html b/docs/buildroot.html index 44aadf43e0..144461298f 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -335,19 +335,14 @@ completely rebuild your toolchain and tools, these changes will be lost. -
  • Customize the target filesystem skeleton available under - fs/skeleton/. You can customize configuration files or other - stuff here. However, the full file hierarchy is not yet present - because it's created during the compilation process. Therefore, you - can't do everything on this target filesystem skeleton, but changes to - it do remain even if you completely rebuild the cross-compilation - toolchain and the tools.
    You can also customize the - target/generic/device_table.txt file, which is used by the - tools that generate the target filesystem image to properly set - permissions and create device nodes.
    These customizations are - deployed into output/target/ just before the actual image - is made. Simply rebuilding the image by running make should propagate - any new changes to the image.
    • +
  • Create your own target skeleton. You can start with + the default skeleton available under fs/skeleton + and then customize it to suit your + needs. The BR2_ROOTFS_SKELETON_CUSTOM + and BR2_ROOTFS_SKELETON_CUSTOM_PATH will allow you + to specify the location of your custom skeleton. At build time, + the contents of the skeleton are copied to output/target before + any package installation.
  • Add support for your own target in Buildroot, so that you have your own target skeleton (see this -- 2.30.2