Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [v2] Allow to run severals post build scripts instead of only one
Date: Mon, 09 Jul 2012 13:32:08 +0200	[thread overview]
Message-ID: <4FFAC138.7000805@mind.be> (raw)
In-Reply-To: <5239_1341822603_4FFA968B_5239_239_2_1341822615-22895-1-git-send-email-philippe.reynes@sagemcom.com>

On 07/09/12 10:30, Philippe Reynes wrote:
> Using severals post build scripts is usefull to share
> script between severals boards/projects.
>
> Signed-off-by: Philippe Reynes<philippe.reynes@sagemcom.com>
> ---
>   Makefile                 |    3 ++-
>   target/generic/Config.in |   11 ++++++-----
>   2 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index b80477f..56833da 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -449,7 +449,8 @@ endif
>
>   ifneq ($(BR2_ROOTFS_POST_BUILD_SCRIPT),"")
>       @$(call MESSAGE,"Executing post-build script")
  This should be plural now :-)  Or "script(s)".

> -    $(BR2_ROOTFS_POST_BUILD_SCRIPT) $(TARGET_DIR)
> +    @$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_BUILD_SCRIPT)), \
> +        $(s) $(TARGET_DIR);)
>   endif
>
>   ifeq ($(BR2_ENABLE_LOCALE_PURGE),y)
> diff --git a/target/generic/Config.in b/target/generic/Config.in
> index 88f0718..b987331 100644
> --- a/target/generic/Config.in
> +++ b/target/generic/Config.in
> @@ -138,15 +138,16 @@ config BR2_ROOTFS_POST_BUILD_SCRIPT
>       string "Custom script to run before creating filesystem images"
>       default ""
>       help
> -      Specify a script to be run after the build has finished and before
> -      Buildroot starts packing the files into selected filesystem images.
> +      Specify a space-separated list of scripts to be run after the build
> +      has finished and before Buildroot starts packing the files into
> +      selected filesystem images.
>
>         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.
> +      These scripts are called with the target directory name as first and
> +      only argument. Make sure the exit code of those scripts are 0,
> +      otherwise make will stop after calling them.

  With this patch, this is no longer true except for the last script in the list.
To fix that, it should be something like:

     @$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_BUILD_SCRIPT)), \
         $(s) $(TARGET_DIR) || exit 1;)

Or even better (untested):

     @$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_BUILD_SCRIPT)), \
         $(s) $(TARGET_DIR)$(sep))


  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-07-09 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  8:30 [Buildroot] [PATCH] [v2] Allow to run severals post build scripts instead of only one Philippe Reynes
2012-07-09 11:32 ` Arnout Vandecappelle [this message]

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=4FFAC138.7000805@mind.be \
    --to=arnout@mind.be \
    --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