> If you run bjam with "-d2" option, you'll see all the command lines, which
> should be enough to find out which libraries are beeing linked.

It appears that I don't really need -d2 to get a linker line. bjam prints ot
togerther with error anyway:

mwld -search -maxerrors 5 -maxwarnings 20 -export
dllexport -nowraplines -g -subsystem console     -o
"..\..\..\libs\test\test\bin\prg_exec_fail1.test\cwpro8\debug\runtime-link-d
ynamic\prg_exec_fail1.exe"
@"..\..\..\libs\test\test\bin\prg_exec_fail1.test\cwpro8\debug\runtime-link-
dynamic\prg_exec_fail1.CMD"

..\..\..\libs\test\test\bin\prg_exec_fail1.test\cwpro8\debug\runtime-link-dy
namic\prg_exec_fail1.CMD:

"..\..\..\libs\test\test\bin\prg_exec_fail1.test\cwpro8\debug\runtime-link-d
ynamic\prg_exec_fail1.obj"
"..\..\..\libs\test\build\bin\libboost_prg_exec_monitor.lib\cwpro8\debug\run
time-link-dynamic\libboost_prg_exec_monitor.lib"
"..\..\..\libs\test\build\bin\libboost_prg_exec_monitor.lib\cwpro8\debug\run
time-link-dynamic\libboost_prg_exec_monitor.lib"

Does it help?

Gennadiy.





_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply via email to