[Buildroot] [PATCH v2 2/5] docs/manual: mention the new post-image mechanism
thomas.petazzoni at free-electrons.com
Wed Feb 6 21:49:03 UTC 2013
Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
* Fix typos noticed by Yann.
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 fa04d85..f1d336a 100644
@@ -55,3 +55,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 you 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 space-separated 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+.
More information about the buildroot