Re: [jamboost] build-dir/ALL_LOCATE_TARGET behaviour

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-09-16 11:04:16

[2003-09-16] Vladimir Prus wrote:

>
>I'm looking at 
>
> http://zigzag.cs.msu.su:7814/scarab/issues/id/BB7
>
>which says that V2 project cannot be built from a readonly medium. The 
>solution for a single project is simple, but assume the following directory 
>structure
>
> /cdrom
> project
> lib1
> lib2
>
>In project1 I run, say 
>
> bjam --build-dir=/home/ghost/build/project
>
>and targets will be generated to the specified directory. What is "project" 
>depends on "lib1" and "lib2"? Where should targets be generated?
>
>And, BTW, if V1 now supports multiple projects, how it solves this
question?

Some of those same questions are why in the v1 cross-project changes I moved
to putting the generated binaries into a single integrated project-root
level "bin" directory. Basically it sets ALL_LOCATE_TARGET to:
<project-root>/bin/<project-name>/path/to/sub-project, for each project
used. That keeps the targets all unique.

In your example, assuming all those directories are individual projects, you
would end up with:

build/project/bin/project/...
build/project/bin/lib1/...
build/project/bin/lib2/...

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq