I have found it convenient that Boost uses pragmas to link with its libraries, because it would otherwise be a matter of trial and error to determine which of the multitude of libraries created by a default bjam build is the one I need. As it is, I only have to search for the ones the linker can't find, and add their paths to Visual Studio. If you want to suppress that feature, simply use the /NODEFAULT linker option. Keith MacDonald "Bennett, Patrick" <Patrick.Bennett@inin.com> wrote in message news:260A0A30F9017945932CC4F7B911B33901786BF5@i3mail1.i3domain.inin.com...
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Victor A. Wagner Jr. Sent: Wednesday, May 25, 2005 10:34 PM To: boost@lists.boost.org Subject: RE: [boost] Customer Friendlier Boost Installation
When it comes to compiling and linking, I don't want the compiler or linker including anything more than I explicitly told it to include.
If you disagree, well, hey, I guess we'll just have to agree to disagree.
Cheers... Patrick Bennett
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost