From patchwork Wed Jan 16 19:09:49 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [2/5] docs/manual: mention the new post-image mechanism Date: Wed, 16 Jan 2013 09:09:49 -0000 From: Thomas Petazzoni X-Patchwork-Id: 212991 Message-Id: <1358363393-29977-3-git-send-email-thomas.petazzoni@free-electrons.com> To: buildroot@uclibc.org Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN" Acked-by: Luca Ceresoli --- docs/manual/customize-rootfs.txt | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/manual/customize-rootfs.txt b/docs/manual/customize-rootfs.txt index 6399699..66e38dc 100644 --- a/docs/manual/customize-rootfs.txt +++ b/docs/manual/customize-rootfs.txt @@ -50,3 +50,18 @@ there are a few ways to customize the resulting target filesystem. target root filesystem in +package/customize/source+, and then enable this special package in the configuration system. _This method is marked as deprecated_. + +Note also that if want to perform some specific actions *after* all +filesystem images have been created (for example to automatically +extract your root filesystem tarball in a location exported by your +NFS server, or to create a special firmware image that bundles your +root filesystem and kernel image, or any other custom action), you can +specify a list of scripts in the +BR2_ROOTFS_POST_IMAGE_SCRIPT+ +configuration option. Each of those scripts will be called, with the +path to the +images+ output directory as first and unique argument, +and will be executed with the main Buildroot source directory as the +current directory. Also, just like for the _post-build scripts_ +mentionned above, you also have access to the following environment +variables from your _post-image scripts_: +BUILDROOT_CONFIG+, ++HOST_DIR+, +STAGING_DIR+, +TARGET_DIR+, +BINARIES_DIR+ and ++BASE_DIR+.