I've downloaded Boost 1.31.0 and tried to build it using the standard bjam procedure from the getting started document. I have WinXP/Home and the standard edition of VC7.1 (.NET 2003). I've tried both the vc7.1 and the vc7.1-stlport toolsets. In both cases the following libraries are generated: boost_date_time boost_filesystem boost_signals boost_thread libbost_date_time libbost_prg_exec_monitor libbost_regex libbost_signals libbost_test_exec_monitor libbost_unit_test_framework During the build process I get compiler warnings because the standard version of VC won't do advanced optimizations, but otherwise there seems to be no problem. Bjam stops after having generated the above libraries. Shouldn't there be more? What's the difference between those starting with boost and those starting with libboost? Do I have to somehow generate the remaining libraries separately? Thanks!
On Monday 15 March 2004 06:21 am, Ulf Johansson wrote:
During the build process I get compiler warnings because the standard version of VC won't do advanced optimizations, but otherwise there seems to be no problem. Bjam stops after having generated the above libraries. Shouldn't there be more? What's the difference between those starting with boost and those starting with libboost? Do I have to somehow generate the remaining libraries separately?
The majority of Boost libraries do not require any extra compilation, because all of the code is in the library headers. Many Boost users don't need to compile anything separately. Doug
----- Original Message -----
From: "Douglas Gregor"
On Monday 15 March 2004 06:21 am, Ulf Johansson wrote:
During the build process I get compiler warnings because the standard version of VC won't do advanced optimizations, but otherwise there seems to be no problem. Bjam stops after having generated the above libraries. Shouldn't there be more? What's the difference between those starting with boost and those starting with libboost? Do I have to somehow generate the remaining libraries separately?
The majority of Boost libraries do not require any extra compilation, because all of the code is in the library headers. Many Boost users don't need to compile anything separately.
Doug _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Thank you Doug, Is it fair to say that I've generated what libraries there was to generate in the distribution and all the other Boost libraries are represented by source code and templates in include files? Well, I should have started using them instead of worrying about not having them -:) But I'm new to C++ and Boost so all this is a little overwhelming.
Ulf Johansson wrote:
Is it fair to say that I've generated what libraries there was to generate in the distribution and all the other Boost libraries are represented by source code and templates in include files?
Looking at the list you gave almost all the libraries that can be generated got generated. The ones you are missing are for Boost.Python, which I imagine you did not install or configure so it did not build it. But if you are going to use Boost.Python there are additional instructions for how to build it in its documentation.
Well, I should have started using them instead of worrying about not having them -:) But I'm new to C++ and Boost so all this is a little overwhelming.
Perhaps ;-) But at least I like seeing that people are not having major problems with the new build+install procedure :-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
participants (3)
-
Douglas Gregor -
Rene Rivera -
Ulf Johansson