RE: [jamboost] v2: build-project rule

From: Reece Dunn (msclrhd_at_[hidden])
Date: 2004-08-12 17:23:28

Toon Knapen wrote:
>I would like to build the targets in two subdirectories when bjam is
>invoked in the parent directory. So I found out about the build-project
>rule. But can the Jamfile contain multiple build-project's?
>
><begin Jamfile>
>build-project library1 ;
>build-project library2 ;
><end Jamfile>

yes.

>When I do this, my bjam crashes with a segmentation fault. I already
>wrote a few messages on the ml about memory corruption in strings.c.
>Well it is only in this situation (when having multiple build-project's
>in my Jamfile) that I get a segmentation fault. I valgrinded bjam on a
>lot of other projects (which contain no multiple build-projects) and got
>zero warnings from valgrind.

Hmm... I don't have a problem with my bjam when using multiple 
build-projects.

Does the source tree match up, i.e. a library1 folder with the appropriate 
stuff (Jamfile, project-root.jam) with the relevant code.

NOTE: It is not necessary to have project-root.jam or create an explicit new 
project. This is only relevant if you want to alter global project 
configuration stuff, or have a named project id.

If you are creating a named project (i.e. have a project rule in the 
Jamfile), you need to add:
import project ;
project.initialize $(__name__) ;
at the top of the Jamfile to stop bjam complaining (it took me a while to 
work this out, since it is a recent change to project decleration).

Regards,
Reece

_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger 
http://www.msn.co.uk/messenger