[openbeos] Re: Introducing an Jam question to HAIKU Build system

On 2006-12-23 at 21:06:16 [+0100], Jörg Bernau <Joerg.Bernau@xxxxxx> wrote:
> Stephan Assmus schrieb:
> >
> > thanks for your introduction and your plan to port WebKit is a very noble
> > one. I would like to help with this, but I can not before April next year.
> > Are you aware of the Nirvana project on Berlios? <www.berlios.de>. You 
> > will
> > probably find the code in the lemmon branch very interesting.
> >
> > As for the jamfile question, it appears you have copied the Haiku build
> > system?
> >
> >   
> >> calling "jam -a" terminates with the following result:
> >>
> >> don't know how to make <build>settype
> >> don't know how to make <build>mimeset
> >> don't know how to make <build>setversion
> >>     
> >
> > These are "build tools" for which the code is actually part of the Haiku
> > source tree. You would need to copy the source of those, or modify the
> > Jamrules (Ingo would know which one) so that it just uses a prebuilt 
> > version.
> >
> >   
> Well, one fault might be that I overwrote the "BuildConfig" file.

If you just want a build system for your project the Haiku build system might 
be a bit overkill. If you're developing under BeOS and don't need 
cross-compilation a simple jam-based build system might be the easiest way to 
go. In the jamfile snippet you sent in your first mail only the rules in 
lines 3-6 are Haiku build system specific, and I believe you either don't 
need them at all or could replace them by rules built into jam.

If you want to do fancy things and really want to copy Haiku's build system 
note that -- as Stephan mentioned -- there are several build tools included 
in the source tree (among those the three jam complained about). Those in 
turn need a stripped down version of libbe (cf. src/build). If you develop 
under BeOS you can adjust build/jam/BeOSRules to use the native BeOS tools 
instead. For cross-developing under Linux I suppose the quickest solution 
would be to check out the Haiku source tree, create a subdirectory for your 
project, and integrate it into Haiku's build system. Not a permanent 
solution, but one that gets you going instantly.

CU, Ingo

Other related posts: