From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thierry Bultel Date: Thu, 18 Oct 2012 21:21:41 +0200 Subject: [Buildroot] export ARCH and CROSS_COMPILE for the post build script In-Reply-To: <20121018191259.0d9d9843@skate> References: <507F9EFB.60601@wanadoo.fr> <20121018153822.58509c94@skate> <508020C8.8000700@wanadoo.fr> <20121018191259.0d9d9843@skate> Message-ID: <508056C5.3080101@wanadoo.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Le 18/10/2012 19:12, Thomas Petazzoni a ?crit : > Dear Thierry Bultel, > > On Thu, 18 Oct 2012 17:31:20 +0200, Thierry Bultel wrote: > >>>> 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". > Thanks, that is exactly what I need. >> 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 _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 > > Thomas >