Re: [jamboost] [BBv2] Indepent target warnings for response_files

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-06-02 05:59:10

On Thursday 02 June 2005 14:46, Johan Nilsson wrote:
> Hi,
>
> I just noticed (using the latest anonymous CVS version of bjam + bbv2) that
> I consistently get "independent target" warnings for the xxx_cpp.rsp files
> during compilation. A sample output:
>
> ...found 12 targets...
> ...updating 5 targets...
> warning: using independent target <pbin\msvc-7.1\debug>main_cpp.rsp
> msvc.compile.c++ bin\msvc-7.1\debug\main.obj
> bin\msvc-7.1\debug\main_cpp.rsp main.cpp
> msvc.link bin\msvc-7.1\debug\bjam_test.exe bin\msvc-7.1\debug\bjam_test.rsp
> ...updated 5 targets...

This is common annoyance. As soon as Dave and I finish tweaking response 
files, I'll just remove this warning from the code. I don't recall any 
instance where it pointed out a valid problem.

> Also, note the printed <pbin\msvc-7.1\...> directory specification - why
> the extra "p" at the beginning?

Because that's "grist", not a path. 'p' means that the remainder of the grist
if the target path. You techically have an action that searches for a file 
along several directories and copies it to the current one. Then the target 
that is copied to the current with will be

<p.>foo.cpp

and the target that is searched will be

<l.>foo.cpp

We don't know where the file is, so we need to use the location of the current
project inside grist, and must make sure it's not confused with the first
targets.

At least this was the original motivation.

> Another thing (unrelated): is it possible to get rid of the msvc.compile
> .... etc output, and just get the unqualified name of the source file(s)
> during build? That would be "main.cpp" in the above output.

No, it's not possible. I'd like to somehow shorten the lines too -- they often
wrap for me. Maybe, we just need to drop the path from those lines?

- Volodya

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