From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] future of project support
Date: Tue, 21 Apr 2009 08:11:04 +0200 [thread overview]
Message-ID: <877i1esfif.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090420003249.GA18066@cloud.net.au> (Hamish Moffatt's message of "Mon\, 20 Apr 2009 10\:32\:49 +1000")
>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
Hi,
>> Because of the project stuff. There's been discussion about getting
>> rid of that and simply use the external toolchain stuff if you want to
>> build seperate rootfs'es for similar hw, and I'm seriously considering
>> doing so.
Hamish> I'm in favour of some simplification. Here's my usage:
Hamish> I have a few related projects. I want to build them from the
Hamish> same source tree. Ideally I can have them all built within
Hamish> one check-out, so I can quickly make a change and test it in
Hamish> multiple projects (without checking in, updating the other
Hamish> check out etc).
Have you ever used the out-of-tree build feature? I use it all the
time, and it seems to fit this use case. Simply do make
O=/output/dir/for/project1 and all the build / binaries dirs gets in
/output/dir/for/project1.
Hamish> I don't care if everything is rebuilt for each project.. (except the
Hamish> toolchain possibly). I think the current mix of build_arch /
Hamish> project_build_arch is a mess, I'd prefer to have everything in
Hamish> project_build_arch really.
Or simply build_arch if we get rid of the project stuff.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-04-21 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 8:33 [Buildroot] Properly setting up hotplug Sagaert Johan
2009-04-17 8:52 ` Thiago A. Corrêa
2009-04-17 13:56 ` Peter Korsgaard
2009-04-17 14:19 ` Lloyd Sargent
2009-04-17 13:36 ` Peter Korsgaard
2009-04-20 0:32 ` [Buildroot] future of project support Hamish Moffatt
2009-04-21 6:11 ` Peter Korsgaard [this message]
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=877i1esfif.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.