<lib> problem resolved

From: Mark Coletti (mcoletti_at_[hidden])
Date: 2002-11-18 17:14:15

It turns out that the linker command line item does NOT explicitly
include libraries specified via <lib>. Instead it spirits them away
in a file in the "bin" directory hiearchy and uses the '@' (in the
case of 'msvc' tool context) to include them in the linker invocation
command line. So, it turns out that it was finding the library after
all. ~~~:-\

However, this brings up a debugging/aesthetics issue. Why separate
out the libraries into a file spirited deep away in the "bin"
hierarchy? Doesn't it make more sense to just include the libraries
on the same command line? Not doing so can be misleading to Boost Jam
neophytes (as I just demonstrated).

Now I've got to track down the linker errors. Joy.

Cheers!

Mark
-- 
Mark Coletti | mailto:mcoletti_at_[hidden] | http://www.lychnobite.org/
If it ain't broke, it ain't Micro$oft!