It seems like they are have been added unconditionally. I have build several projects using visual studio and in all of them the aforementioned libraries are added along with others.
I haven't compiled anything from command line but I would assume that invoking the linker would include these libraries by default ( will confirm and let you know sometime later).

I would take that bjam chooses to do things differently by default.  Which is alright, but should be documented somewhere, otherwise you run into unexpected troubles.




On Feb 1, 2008 9:40 AM, Vladimir Prus <ghost@cs.msu.su> wrote:
On Friday 01 February 2008 20:26:49 Sandeep Gupta wrote:
> Hi Volodya,
>   Let me rephrase: If the code compiles in visual studio without doing
> anything special (such as  explicitly adding system library) then  I would
> assume that it should also compile with bjam.
>
> If this not so then it should be mentioned somewhere. If it is, then never
> mind but please let me know the link.
>
> In the particular case of RCF (a c++ interprocess communication routine) it
> compiled fine using visual studio but had the aforementioned difficulty with
> bjam. Therefore I asked.
>
> Link for RCF if interested:
> http://www.codeproject.com/KB/threads/Rcf_Ipc_For_Cpp.aspx

Presumably, when you've created a project in Visual Studio, those
libraries were automatically added. I don't know why, and whether they
are added unconditionally, or depending on the type of project your
create, or if the project file for RCF had them, etc. In particular,
if you create console application project, will it still link to those
two libraries?

So, Boost.Build should link to library X automatically if and only
if it's generally impossible to link an application without that
library.

- Volodya


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