Re: [v2] ALL_LOCATE_TARGET capability?

From: David Abrahams (dave_at_[hidden])
Date: 2004-12-10 14:10:43

Vladimir Prus wrote:
> On Friday 10 December 2004 19:03, David Abrahams wrote:
>> Vladimir Prus wrote:
>> > I'd like to have directive like:
>> >
>> > global-build-dir /space/p2/build_dir ;
>> >
>> > which will causes all projects to be build under /space/p2/build_dir,
>> > with paths like
>> >
>> > /space/p2/build_dir/home/ghost/Work/boost
>> > /space/p2/build_dir/home/ghost/Work/boost_rc
>> > /space/p2/build_dir/home/ghost/Work/nm_model
>> >
>> > Maybe, this will solve the "build from read only medium" issue too (if
>> > global build dir can be specified from command line).
>>
>> Whoa there. I didn't realize you meant for this to be global for all
>> users. How is it going to deduce the /home/ghost/Work part? I think 
>> it's enough to make people specify that part explicitly.
> 
> I mean that when you build a project with Jamroot at /home/ghost/Work/boost, 
> the build directory is
> 
> /space/p2/build_dir/home/ghost/Work/boost 
> 
> (Simply global build dir path plus full path to Jamroot (after stripping 
> leading slash from Jamroot path).

Hum. Well, it's plausible I guess. People aren't going to like the
long paths (and we already have limit problems on some OSes).

> And if your Jamroot is at /home/dave/boost, then it will be built to
> 
> /space/p2/build_dir/home/dave/boost
> 
> Of course, it might be possible to strip "/home/ghost".

(As usual) I vote for allowing users to define a rule in xxx-config.jam
that computes where a project will be built based on its path (and
possibly some other info).

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com