From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using buildroot for multiple projects
Date: Fri, 08 Jan 2010 16:24:46 +0000 [thread overview]
Message-ID: <4B475C4E.4010201@carallon.com> (raw)
I have a question about using buildroot for multiple projects.
Currently you can specify different output folders with O= and swap
between configs either by copying the .config and calling make oldconfig
or using make*_defconfig.
This appears to work fine, however the problem is that you can not do
builds of two different projects at the same time. This is because of
the config files in package/config and the top directory of buildroot.
Anyone know why it wouldn't be possible to make it an option as to where
the config files got built to so that they could also be built out of tree?
Looking at the top level makefile it looks relatively straight forward,
however there are a couple of bits I don't quite understand.
Why do we copy $(CONFIG)/buildroot-config to BR2_DEPENDS_DIR? It appears
to be for the headers in$(CONFIG)/buildroot-config/br2 which I assume
are build by conf? Why does the $(CONFIG)/buildroot-config exist where
it is - why not just generate it into BR2_DEPENDS_DIR then there is no
need to copy it?
Who uses .auto.deps? I can't find anyone, yet we seem to patch config
for buildroot so it is created.
Thanks,
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
reply other threads:[~2010-01-08 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B475C4E.4010201@carallon.com \
--to=will_wagner@carallon.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