Skip to contentSkip to conversation

export ARCH and CROSS_COMPILE for the post build script

Buildroot Thierry Bultel 2 participants 5 messages Oct 18, 2012

lore
Share & tools
lore
#0 lore raw

Hello,

Could we make the export of PATH and CROSS_COMPILE to the post-build script ?
This would be really useful for building an external user application in one shot (and I need it in my case).

eg something like this in the top Makefile:

ifneq ($(BR2_ROOTFS_POST_BUILD_SCRIPT),"")

     @$(call MESSAGE,"Executing post-build script")

*ARCH=$(ARCH) CROSS_COMPILE=$(TARGET_CROSS)*
$(BR2_ROOTFS_POST_BUILD_SCRIPT) $(TARGET_DIR)
endif

Of course this could be implemented as an option.

What do you think about it ?

Thanks
Thierry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121018/62f707dd/attachment-0001.html>

#1 lore raw

Dear Thierry Bultel,

Quoted 8 lines · Thierry Bultel

Could we make the export of PATH and CROSS_COMPILE to the post-build script ?
This would be really useful for building an external user application in one shot (and I need it in my case).

eg something like this in the top Makefile:

ifneq ($(BR2_ROOTFS_POST_BUILD_SCRIPT),"")

Quoted 8 lines
     @$(call MESSAGE,"Executing post-build script")

*ARCH=$(ARCH) CROSS_COMPILE=$(TARGET_CROSS)*
$(BR2_ROOTFS_POST_BUILD_SCRIPT) $(TARGET_DIR)
endif

Of course this could be implemented as an option.

What do you think about it ?

Why don't you create a Buildroot package to build your external application? It sounds much more logical.

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#2 lore raw

Le 18/10/2012 15:38, Thomas Petazzoni a ?crit :

Quoted 17 lines

Dear Thierry Bultel,

Quoted 13 lines · Thierry Bultel

Could we make the export of PATH and CROSS_COMPILE to the post-build script ?
This would be really useful for building an external user application in one shot (and I need it in my case).

eg something like this in the top Makefile:

ifneq ($(BR2_ROOTFS_POST_BUILD_SCRIPT),"")

      @$(call MESSAGE,"Executing post-build script")

*ARCH=$(ARCH) CROSS_COMPILE=$(TARGET_CROSS)*
$(BR2_ROOTFS_POST_BUILD_SCRIPT) $(TARGET_DIR)
endif

Quoted 5 lines
Quoted 3 lines

Of course this could be implemented as an option.

What do you think about it ?

Why don't you create a Buildroot package to build your external application? It sounds much more logical.

That was my very first idea.
But I wanted to keep the Buildroot tree unchanged.

And at the time I took the decision, I did not find out how to make such a package be built after all the others. So "post build" sounded appropriate.

Quoted 1 line

Thomas

#3 lore raw

Dear Thierry Bultel,

Quoted 6 lines · Thierry Bultel
Quoted 3 lines
Quoted 1 line

What do you think about it ?

Why don't you create a Buildroot package to build your external application? It sounds much more logical.

That was my very first idea.
But I wanted to keep the Buildroot tree unchanged.

You can keep your Buildroot tree unchanged and still have Buildroot packages for your own application:

buildroot/
mysystem/
mysystem.mk
packages/
myapp/myapp.mk
myotherapp/myotherapp.mk

And then you can do something like this in mysystem.mk:

BR2_PACKAGE_MYAPP=y
BR2_PACKAGE_MYOTHERAPP=y
include packages/*/*.mk

And your Buildroot configuration, set BR2_PACKAGE_OVERRIDE_FILE to "$(TOPDIR)/../system.mk".

Quoted 2 lines

And at the time I took the decision, I did not find out how to make such a package be built after all the others.

Why would you want to do that absolutely? If your packages have dependencies, put them in <yourpackage>_DEPENDENCIES, and your package will be built after its required dependencies. There is no reason to build after *all* packages.

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#4 lore raw

Le 18/10/2012 19:12, Thomas Petazzoni a ?crit :

Quoted 21 lines

Dear Thierry Bultel,

Quoted 6 lines · Thierry Bultel
Quoted 3 lines
Quoted 1 line

What do you think about it ?

Why don't you create a Buildroot package to build your external application? It sounds much more logical.

That was my very first idea.
But I wanted to keep the Buildroot tree unchanged.

You can keep your Buildroot tree unchanged and still have Buildroot packages for your own application:

buildroot/
mysystem/
mysystem.mk
packages/
myapp/myapp.mk
myotherapp/myotherapp.mk

Quoted 9 lines

And then you can do something like this in mysystem.mk:

BR2_PACKAGE_MYAPP=y
BR2_PACKAGE_MYOTHERAPP=y
include packages/*/*.mk

And your Buildroot configuration, set BR2_PACKAGE_OVERRIDE_FILE to "$(TOPDIR)/../system.mk".

Thanks, that is exactly what I need.

Quoted 7 lines
Quoted 2 lines

And at the time I took the decision, I did not find out how to make such a package be built after all the others.

Why would you want to do that absolutely? If your packages have dependencies, put them in <yourpackage>_DEPENDENCIES, and your package will be built after its required dependencies. There is no reason to build after *all* packages.

You are right, even if I need quite a lot of things, this does not mean all the packages. And it is valuable to maintain a known list of dependencies.

Thanks
Thierry

Quoted 3 lines

Thomas