Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add support for custom post-build script
Date: Wed, 15 Jul 2009 11:21:05 +0200	[thread overview]
Message-ID: <20090715092105.GG9464@buzzloop.caiaq.de> (raw)
In-Reply-To: <1247086018-18816-1-git-send-email-daniel@caiaq.de>

What about this one?


On Wed, Jul 08, 2009 at 10:46:58PM +0200, Daniel Mack wrote:
> The config help text says it all:
> 
>   Specify a script to be run after the build has finished and before
>   the BR2 starts packing the files into selected packages.
> 
>   This gives users the oportunity to do board-specific cleanups,
>   add-ons and the like, so the generated files can be used directly
>   without further processing.
> 
>   The script is called with the target directory name as first and
>   only argument. Make sure the exit code of that script is 0,
>   otherwise make will stop after calling it.
> 
> Signed-off-by: Daniel Mack <daniel@caiaq.de>
> Cc: Sven Neumann <s.neumann@raumfeld.com>
> ---
>  Makefile         |    4 ++++
>  target/Config.in |   15 +++++++++++++++
>  2 files changed, 19 insertions(+), 0 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index 76dd2cd..dbeede5 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -360,6 +360,10 @@ endif
>  	find $(TARGET_DIR) -type f -perm +111 | xargs $(STRIPCMD) 2>/dev/null || true
>  	$(TARGET_LDCONFIG) -r $(TARGET_DIR) 2>/dev/null
>  
> +ifneq ($(BR2_ROOTFS_POST_BUILD_SCRIPT),"")
> +	$(BR2_ROOTFS_POST_BUILD_SCRIPT) $(TARGET_DIR)
> +endif
> +
>  ifeq ($(BR2_ENABLE_LOCALE_PURGE),y)
>  LOCALE_WHITELIST=$(PROJECT_BUILD_DIR)/locales.nopurge
>  LOCALE_NOPURGE=$(strip $(subst ",,$(BR2_ENABLE_LOCALE_WHITELIST)))
> diff --git a/target/Config.in b/target/Config.in
> index 87abbe6..dbdc2d6 100644
> --- a/target/Config.in
> +++ b/target/Config.in
> @@ -12,6 +12,21 @@ config BR2_ROOTFS_SUFFIX
>  	help
>  	  Add a custom string to the end of the root file system name.
>  
> +config BR2_ROOTFS_POST_BUILD_SCRIPT
> +	string "Custom script to run before packing files"
> +	default ""
> +	help
> +	  Specify a script to be run after the build has finished and before
> +	  the BR2 starts packing the files into selected packages.
> +
> +	  This gives users the oportunity to do board-specific cleanups,
> +	  add-ons and the like, so the generated files can be used directly
> +	  without further processing.
> +
> +	  The script is called with the target directory name as first and
> +	  only argument. Make sure the exit code of that script is 0,
> +	  otherwise make will stop after calling it.
> +
>  comment "filesystem for target device"
>  
>  source "target/cramfs/Config.in"
> -- 
> 1.6.3.1
> 

  reply	other threads:[~2009-07-15  9:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 20:46 [Buildroot] [PATCH] Add support for custom post-build script Daniel Mack
2009-07-15  9:21 ` Daniel Mack [this message]
2009-07-16  4:14   ` Paul Archer
2009-07-25 21:14 ` Peter Korsgaard
2009-07-27 11:58   ` Daniel Mack
2009-07-27 12:17     ` Peter Korsgaard
2009-07-27 12:38       ` Daniel Mack
2009-07-27 12:48     ` Peter Korsgaard
2009-07-27 12:26   ` Marcelo Martins Maia do Couto
  -- strict thread matches above, loose matches on Subject: below --
2009-07-10 16:26 nfrench at xtale.biz
2009-07-10 18:43 ` Daniel Mack
2009-07-11 19:34 nfrench at xtale.biz
2009-07-13  3:14 ` Paul Archer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090715092105.GG9464@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox