From 53fd73611c93f55215356444a15d3f615fd74003 Mon Sep 17 00:00:00 2001 From: Daniel Mack Date: Mon, 27 Jul 2009 13:58:38 +0200 Subject: [PATCH] docs: describe BR2_ROOTFS_POST_BUILD_SCRIPT Signed-off-by: Daniel Mack Signed-off-by: Peter Korsgaard --- docs/buildroot.html | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/buildroot.html b/docs/buildroot.html index e97d6011f7..b49208c273 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -37,6 +37,7 @@
  • Use an external toolchain
  • Location of downloaded packages
    • +
  • Adapting the rootfs for own binaries
  • Extending Buildroot with more Software
  • Resources
    • @@ -877,6 +878,22 @@ It allows to generate toolchains based on uClibc, glibc and eglibc for a wide range of architectures, and has good community support.

    +

    Adapting the rootfs + for own binaries

    + +

    When using BR2 in an environment where own software binaries or + static data should be part of the generated rootfs package, the + BR2_ROOTFS_POST_BUILD_SCRIPT feature might interest + you. You can specify a command here which is called after BR2 + built all the selected software, but before the the rootfs + packages are assembled. The destination rootfs folder is given as + first argument. You can add own components here, change + default configurations and remove unwanted files.

    +

    You should, however, use that feature with care. Whenever you + find that a certain package generates wrong or unneeded files, you + should rather fix than package than working around it with a + cleanup script.

    +

    Extending Buildroot with more software