From: Johan Nilsson (johan.nilsson_at_[hidden])
Date: 2004-10-20 08:12:26
"Vladimir Prus" <ghost_at_[hidden]> wrote in message
>> > That should not happen? Which V2 version do you use? In M10
>> > (http://zigzag.lvk.cs.msu.su/~ghost/Milestone_10_preview/), which is
>> > due
>> > soon, the 'unit-test' rule adds the proper DLL paths.
>> I'm using the latest cvs version. Is there anyway to run the staged file
>> using the cvs version, preserving tags etc?
> None that I know, as unit-test is supposed to do that. A future version
> have "notfile" target which allows to run arbitrary actions, but:
> - I'm not sure that will be convenient for running staged exes
> - It's not implemented yet
Isn't notfile a "built-in target" already in Jam/MR?
>> How can the unit-test rule know the proper DLL paths? I've got a couple
>> import libraries under deps/libs as well, with the corresponding DLLs
> Good catch. On Linux, if exe (or unit-test) uses a shared lib file
> prebuilt one), it will add the right paths. I've just realized that import
> libs on windows do not work as nice.
> However, you can try:
> lib whatever : : <file>whatever.lib <file>whatever.dll ;
> so that V2 knows there's DLL involved.
How about the paths in this case?
> Or you can add <dll-path>deps/libs to your project requirements to make
> unit-test add that path when running tests.
I assume you mean <dll-path>bin ?
Btw, how that implemented? Do you set the path in a .cmd file that runs the
Many thanks for all your replies.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk