In a multidirectory project I have a Jamfile.v2 that builds
a library.
The library builds on top of another library, so I want to
add the other
library as a usage requirement. As I understand it, I
should be able to
write either (A):
project boost_build_test/dir2 ;
lib lib2 : test.cpp : : <source>../dir1//lib1 ;
or (B):
project boost_build_test/dir2
: usage-requirements <source>../dir1//lib1 ;
lib lib2 : test.cpp : ;
I have then an executable target that uses lib2. If this
target is
declared at a different directory level that dir2, then (A)
suceeds, but
(B) complains it is unable to find target ../dir1//lib1. I
have tried
this on windows using msvc and gcc toolsets.
Attached is a zipfile demonstrating the above (run bjam on
dir2/dir21//bin21 )
Is this a misunderstanding on my part that (A) and (B)
should be
equivalent (in this regard), or is this a bug?
Regards,
Hugo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
