From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] export ARCH and CROSS_COMPILE for the post build script
Date: Thu, 18 Oct 2012 19:12:59 +0200 [thread overview]
Message-ID: <20121018191259.0d9d9843@skate> (raw)
In-Reply-To: <508020C8.8000700@wanadoo.fr>
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".
> 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
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-18 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 6:17 [Buildroot] export ARCH and CROSS_COMPILE for the post build script Thierry Bultel
2012-10-18 13:38 ` Thomas Petazzoni
2012-10-18 15:31 ` Thierry Bultel
2012-10-18 17:12 ` Thomas Petazzoni [this message]
2012-10-18 19:21 ` Thierry Bultel
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=20121018191259.0d9d9843@skate \
--to=thomas.petazzoni@free-electrons.com \
--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