[Buildroot] future of project support

Peter Korsgaard jacmet at uclibc.org
Tue Apr 21 06:11:04 UTC 2009

>>>>> "Hamish" == Hamish Moffatt <hamish at cloud.net.au> writes:


 >> 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

 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

More information about the buildroot mailing list