Re: [jamboost] [BBv2] [source-location] - Using this variable in compile and link actions

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-07-07 05:33:26

On Thursday 07 July 2005 14:20, Peter Foley wrote:
> Hi List,
>
> During the development of the wix.jam file to make it easier for me to
> develop I hard coded various values. I am at the stage where I am trying
> to remove the bit where I hardcode "../src" (see the compile and link
> actions below):
>
> ----
> actions compile
> {
> $(.CC) -nologo "$(OPTIONS)" -d"$(DEFINES)" -I../src/"$(INCLUDES)" -out
> "$(<)" "$(>)"
> }

This is strange. Why do you prepend source dir? I suspect that it won't work. 
Say, you have

<include>foo

If this happens in child Jamfile, when building from top-level dir this will 
be translated to something like.

<include>subproject1/subproject2/build/foo

Concatenating it with "subproject1/subproject2/build/../src (the source 
location) will give:

subproject1/subproject2/src/subproject1/subproject2/build/foo

which is likely to be wrong.

Either we need to decide that <include> should be treated relative to source 
location, and not Jamfile location (no opinion yet), or you'd have to use

<include>../src/whatever

Note also that source-location can contain several directories, which 
complicates the matter even more.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2