[haiku-development] Re: Disable creating an image on the default "build" target
- From: André Braga <meianoite@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 6 Jul 2009 23:45:39 -0300
2009/7/6 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> Untested, but you get the idea...
I *so* don't get the idea as the Jamfile language is completely
foreign to me, but consider it tested now :)
Works okay, except that it doesn't build many add-ons. Naturally,
running jam -q @the-actual-profile after the jam @all creates those
add-ons and writes everything to disk just fine.
Seems that nothing is missing, as I'm composing this from a booted
Haiku r31435 that was built following this workflow, and there's
something to be said about building a whole operating system in less
than 20 minutes whose build system handles a 8-way parallel invocation
like a walk in the park :D
Fantastic job!
Oh, and I believe mmadia can use this trick to work around the
multiple fs_shell invocation issue, by building the architectures and
compiler targets in parallel, and in the end call special profiles
sequentially to build the images.
Cheers,
A.
Other related posts: