Re: [jamboost] Lost Usability

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-04-28 09:15:13

On Thursday 28 April 2005 17:41, David Abrahams wrote:
> I was building in libs/python/test and there was an error in something
> from libs/python/build/type_id.cpp. In v1 I used to just write
>
> bjam -d+2 type_id.obj
>
> and it would try to update any target called "type_id.obj." That no
> longer works. How do I do it?
>
>
> bjam -d+2 --v2 msvc-7.1 /boost/libs/python/build//type_id.obj
>
> doesn't work either.

I agree that it's not nice, but I'm not sure what we can do. In V1, first 
complete dependency graph was built, and the corresponding jam target was 
updated. In V1, we only build dependency graph for the explicitly requested 
main target, and in this case, no "type_id.obj" main target is declared.

I think it's possible, however, to check if target main 'type_id.obj' exists 
in Jamfile. If not, we'll assume it's a jam target. Implementing this, I get:

$ bjam hello.o
notice: could not find main target hello.o
notice: assuming it's a name of file to create
...found 8 targets...
...updating 4 targets...
MkDir1 bin
MkDir1 bin/gcc
MkDir1 bin/gcc/debug
gcc.compile.c++ bin/gcc/debug/hello.o
...updated 4 targets...

I've committed the change, let me know if it works for you.

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