[Buildroot] [PATCH] Add support for custom post-build script

[Buildroot] [PATCH] Add support for custom post-build script

[Daniel Mack]

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

[Buildroot] [PATCH] Add support for custom post-build script

[Daniel Mack]

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
> 

[Buildroot] [PATCH] Add support for custom post-build script

[Paul Archer]

Code seems fine by me. It will be useful for some people.

On Wed, Jul 15, 2009 at 7:21 PM, Daniel Mack<daniel@caiaq.de> wrote:
> 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
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 
----
Regards
Paul Archer
ptarcher at gmail.com

[Buildroot] [PATCH] Add support for custom post-build script

[Peter Korsgaard]

>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:

Hi,

 Daniel> The config help text says it all: Specify a script to be run
 Daniel> after the build has finished and before the BR2 starts
 Daniel> packing the files into selected packages.

 Daniel> This gives users the oportunity to do board-specific
 Daniel> cleanups, add-ons and the like, so the generated files can be
 Daniel> used directly without further processing.

 Daniel> The script is called with the target directory name as first
 Daniel> and only argument. Make sure the exit code of that script is
 Daniel> 0, otherwise make will stop after calling it.

I have normally done this by simply running make twice - E.G. build
the rootfs, fixup anything you need under project_build_*/*/root and
run make again to regenerate the rootfs.

But ok, I can see the desire for such a script. I'll apply it now,
thanks.

It would be good to have a note about it in the documentation - Could
I get you to add a short note about it in docs/buildroot.html?

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] Add support for custom post-build script

[Daniel Mack]

On Sat, Jul 25, 2009 at 11:14:57PM +0200, Peter Korsgaard wrote:
> >>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:
> 
>  Daniel> The config help text says it all: Specify a script to be run
>  Daniel> after the build has finished and before the BR2 starts
>  Daniel> packing the files into selected packages.
> 
>  Daniel> This gives users the oportunity to do board-specific
>  Daniel> cleanups, add-ons and the like, so the generated files can be
>  Daniel> used directly without further processing.
> 
>  Daniel> The script is called with the target directory name as first
>  Daniel> and only argument. Make sure the exit code of that script is
>  Daniel> 0, otherwise make will stop after calling it.
> 
> I have normally done this by simply running make twice - E.G. build
> the rootfs, fixup anything you need under project_build_*/*/root and
> run make again to regenerate the rootfs.
> 
> But ok, I can see the desire for such a script. I'll apply it now,
> thanks.
> 
> It would be good to have a note about it in the documentation - Could
> I get you to add a short note about it in docs/buildroot.html?

Sure, see below.

Thanks!

Daniel

[Buildroot] [PATCH] Add support for custom post-build script

[Peter Korsgaard]

>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:

Hi,

 >> It would be good to have a note about it in the documentation - Could
 >> I get you to add a short note about it in docs/buildroot.html?

 Daniel> Sure, see below.

Thanks! One comment:

 Daniel> +      find that a certain package generates wrong or unneeded files, you
 Daniel> +      should rather fix than package than shipping your way around it
 Daniel> +      with a cleanup script.</p>

I think '.. than working around it with a cleanup script.' sounds a
bit better - OK with you?


-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] Add support for custom post-build script

[Daniel Mack]

On Mon, Jul 27, 2009 at 02:17:31PM +0200, Peter Korsgaard wrote:
> Thanks! One comment:
> 
>  Daniel> +      find that a certain package generates wrong or unneeded files, you
>  Daniel> +      should rather fix than package than shipping your way around it
>  Daniel> +      with a cleanup script.</p>
> 
> I think '.. than working around it with a cleanup script.' sounds a
> bit better - OK with you?

Of course, go ahead :)

[Buildroot] [PATCH] Add support for custom post-build script

[Peter Korsgaard]

>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:

 >> It would be good to have a note about it in the documentation - Could
 >> I get you to add a short note about it in docs/buildroot.html?

 Daniel> Sure, see below.

Thanks, committed.

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] Add support for custom post-build script

[Marcelo Martins Maia do Couto]

Hi,

   I'm engineer and would like to learn how i use buildroot and uclinux
together... I searched in google and a lot of media but i can't found... And
you have problems in compile buildroot in x86_64 systems? In my slackware64
can't build this...

   Thanks for any reply.

Eng. Marcelo Martins Maia do Couto
Engenheiro de Desenvolvimento
Coordenador de TI
Professor de Sistemas Operacionais/Redes/Hardware
E-mail: marcelo.m.maia at gmail.com
Site: www.marcelocouto.net
Skype: marcelo_m_maia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090727/31301ece/attachment.htm>

[Buildroot] [PATCH] Add support for custom post-build script

[nfrench at xtale.biz]

I am currently building my app using the tools in staging_dir to
build my app then I mount the built ext2 from binaries cp my program on
and build a new ext2

Is there a standard why to do this .ie
this custom post-build

would it be possible to document how to
add a simple Hello World app.? So that it gets built? with
buildroot or have I missed somthing in the docs.

Thanks

Nick


> 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
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
>
http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090710/2de3d73b/attachment.htm>

[Buildroot] [PATCH] Add support for custom post-build script

[Daniel Mack]

On Fri, Jul 10, 2009 at 04:26:39PM -0000, nfrench at xtale.biz wrote:
> I am currently building my app using the tools in staging_dir to
> build my app then I mount the built ext2 from binaries cp my program on
> and build a new ext2

This is exactly what I want to avoid. I know it is possible, but using
the post-build script method is faster, more logic and more straight
forward.

> Is there a standard why to do this .ie
> this custom post-build

Well, it's up to you what you do with that script. You'll be fed with
the target rootfs as $1 and could then do something like

	cp /path/to/your/hello $1/usr/bin/

Or remove unwanted files etc. Up to you.

> would it be possible to document how to
> add a simple Hello World app.? So that it gets built? with
> buildroot or have I missed somthing in the docs.

No, don't confuse that. Your application will not be built by buildroot
by the post-build script.

If you want to do that, you need to add your own package. See the
package/ folder how others do that. And if that package is building a
publically available project, please consider sending a patch back to
this list so everybody can benefit from it.

Daniel

[Buildroot] [PATCH] Add support for custom post-build script

[nfrench at xtale.biz]

Thanks Daniel

It would be nice to have a proto type package aka
hello world for us first timers. As for me being able to build for two
different platforms 32bit / 64bit is great feature of buildroot. At the
moment we have been using lfs for 32 bit and 64 bit. Does a package have
to have a network location for download as my prototype code / initial
program ideas go through many revisions before they even get to that stage
:-).

Nick

> On Fri, Jul 10, 2009 at 04:26:39PM
-0000, nfrench at xtale.biz wrote:
>> I am currently building my
app using the tools in staging_dir to
>> build my app then I
mount the built ext2 from binaries cp my program on
>> and
build a new ext2
> 
> This is exactly what I want to
avoid. I know it is possible, but using
> the post-build script
method is faster, more logic and more straight
> forward.
> 
>> Is there a standard why to do this .ie
>>
this custom post-build
> 
> Well, it's up to you what you
do with that script. You'll be fed with
> the target rootfs as $1
and could then do something like
> 
> 	cp
/path/to/your/hello $1/usr/bin/
> 
> Or remove unwanted
files etc. Up to you.
> 
>> would it be possible to
document how to
>> add a simple Hello World app.? So that
it gets built? with
>> buildroot or have I missed somthing
in the docs.
> 
> No, don't confuse that. Your application
will not be built by buildroot
> by the post-build script.
> 
> If you want to do that, you need to add your own
package. See the
> package/ folder how others do that. And if that
package is building a
> publically available project, please
consider sending a patch back to
> this list so everybody can
benefit from it.
> 
> Daniel
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090711/8f5f01e8/attachment.htm>

[Buildroot] [PATCH] Add support for custom post-build script

[Paul Archer]

I second the prototype example of a simple helloworld package.

On Sun, Jul 12, 2009 at 5:34 AM, <nfrench@xtale.biz> wrote:
> Thanks Daniel
>
> It would be nice to have a proto type package aka hello world for us first
> timers. As for me being able to build for two different platforms 32bit /
> 64bit is great feature of buildroot. At the moment we have been using lfs
> for 32 bit and 64 bit. Does a package have to have a network location for
> download as my prototype code / initial program ideas go through many
> revisions before they even get to that stage :-).
>
> Nick
>
>> On Fri, Jul 10, 2009 at 04:26:39PM -0000, nfrench at xtale.biz wrote:
>>> I am currently building my app using the tools in staging_dir to
>>> build my app then I mount the built ext2 from binaries cp my program on
>>> and build a new ext2
>>
>> This is exactly what I want to avoid. I know it is possible, but using
>> the post-build script method is faster, more logic and more straight
>> forward.
>>
>>> Is there a standard why to do this .ie
>>> this custom post-build
>>
>> Well, it's up to you what you do with that script. You'll be fed with
>> the target rootfs as $1 and could then do something like
>>
>> cp /path/to/your/hello $1/usr/bin/
>>
>> Or remove unwanted files etc. Up to you.
>>
>>> would it be possible to document how to
>>> add a simple Hello World app.? So that it gets built? with
>>> buildroot or have I missed somthing in the docs.
>>
>> No, don't confuse that. Your application will not be built by buildroot
>> by the post-build script.
>>
>> If you want to do that, you need to add your own package. See the
>> package/ folder how others do that. And if that package is building a
>> publically available project, please consider sending a patch back to
>> this list so everybody can benefit from it.
>>
>> Daniel
>>
>>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>



-- 
----
Regards
Paul Archer
ptarcher at gmail.com