I downloaded Boost 1.35 Head from SVN. I built it with the command: bjam --toolset=msvc-7.1 --NO_ZLIB=0 -sZLIB_SOURCE=C:/Qt/3.3.8/src/3rdparty/zlib install Then I tried to rebuild our app. I got the linking error: LINK : fatal error LNK1104: cannot open file 'libboost_serialization-vc71-mt-1_35.lib' The folder C:/Boost/lib does not contain the file libboost_serialization-vc71-mt-1_35.lib. It seems it was not built. The folder contains boost_serialization-vc71-mt-1_35.dll boost_serialization-vc71-mt-1_35.lib boost_serialization-vc71-mt.lib but no other xxx_serialization_yyy libs. The same happens with the other Boost libs, not just with the serialization lib. Does anyone have any idea what the problem might be, or what additional information I should provide? Thank you, Johan Råde
AMDG Johan Råde wrote:
I downloaded Boost 1.35 Head from SVN. I built it with the command:
bjam --toolset=msvc-7.1 --NO_ZLIB=0 -sZLIB_SOURCE=C:/Qt/3.3.8/src/3rdparty/zlib install
Then I tried to rebuild our app. I got the linking error:
LINK : fatal error LNK1104: cannot open file 'libboost_serialization-vc71-mt-1_35.lib'
The folder C:/Boost/lib does not contain the file libboost_serialization-vc71-mt-1_35.lib. It seems it was not built. The folder contains
boost_serialization-vc71-mt-1_35.dll boost_serialization-vc71-mt-1_35.lib boost_serialization-vc71-mt.lib
but no other xxx_serialization_yyy libs.
The same happens with the other Boost libs, not just with the serialization lib.
Does anyone have any idea what the problem might be, or what additional information I should provide?
--build-type=complete In Christ, Steven Watanabe
Steven Watanabe wrote:
AMDG
Johan Råde wrote:
I downloaded Boost 1.35 Head from SVN. I built it with the command:
bjam --toolset=msvc-7.1 --NO_ZLIB=0 -sZLIB_SOURCE=C:/Qt/3.3.8/src/3rdparty/zlib install
Then I tried to rebuild our app. I got the linking error:
LINK : fatal error LNK1104: cannot open file 'libboost_serialization-vc71-mt-1_35.lib'
The folder C:/Boost/lib does not contain the file libboost_serialization-vc71-mt-1_35.lib. It seems it was not built. The folder contains
boost_serialization-vc71-mt-1_35.dll boost_serialization-vc71-mt-1_35.lib boost_serialization-vc71-mt.lib
but no other xxx_serialization_yyy libs.
The same happens with the other Boost libs, not just with the serialization lib.
Does anyone have any idea what the problem might be, or what additional information I should provide?
--build-type=complete
In Christ, Steven Watanabe
Thank you for a fast reply. Now it's past midnight here, so I'll try your suggestion tomorrow. --Johan
Steven Watanabe wrote:
AMDG
Johan Råde wrote:
I downloaded Boost 1.35 Head from SVN. I built it with the command:
bjam --toolset=msvc-7.1 --NO_ZLIB=0 -sZLIB_SOURCE=C:/Qt/3.3.8/src/3rdparty/zlib install
Then I tried to rebuild our app. I got the linking error:
LINK : fatal error LNK1104: cannot open file 'libboost_serialization-vc71-mt-1_35.lib'
The folder C:/Boost/lib does not contain the file libboost_serialization-vc71-mt-1_35.lib. It seems it was not built. The folder contains
boost_serialization-vc71-mt-1_35.dll boost_serialization-vc71-mt-1_35.lib boost_serialization-vc71-mt.lib
but no other xxx_serialization_yyy libs.
The same happens with the other Boost libs, not just with the serialization lib.
Does anyone have any idea what the problem might be, or what additional information I should provide?
--build-type=complete
Better not, that just wastes energy building zillion variants when you only need one. Instead, request the specific variant you want, like: bjam link=static threading=multi toolset=msvc-7.1 - Volodya
Johan Råde wrote:
Vladimir Prus wrote:
Instead, request the specific variant you want, like:
bjam link=static threading=multi toolset=msvc-7.1
I have been using --toolset=msvc-7.1 etc. Are the double dashes optional?
For the case of 'toolset' two dashes can be present or omitted at will, it does not have any effect on anything. - Volodya
Vladimir Prus wrote:
Instead, request the specific variant you want, like:
bjam link=static threading=multi toolset=msvc-7.1
- Volodya
Question 1: How do I specify that the build should use a dynamic CRT? Question 2: Where do I find the answers to questions such a Question 1? The get started guide contains to little info, the reference manual too much. --Johan
Johan Råde wrote:
Vladimir Prus wrote:
Instead, request the specific variant you want, like:
bjam link=static threading=multi toolset=msvc-7.1
- Volodya
Question 1: How do I specify that the build should use a dynamic CRT?
In general, see answer to question 2. But dynamic CRT is used by default, anyway.
Question 2: Where do I find the answers to questions such a Question 1? The get started guide contains to little info, the reference manual too much.
In Boost.Build documentation. Namely: http://boost.org/boost-build2/doc/html/bbv2/advanced/builtins/features.html - Volodya
Vladimir Prus wrote:
Johan Råde wrote:
Question 1: How do I specify that the build should use a dynamic CRT?
In general, see answer to question 2. But dynamic CRT is used by default, anyway.
Question 2: Where do I find the answers to questions such a Question 1? The get started guide contains to little info, the reference manual too much.
In Boost.Build documentation. Namely: http://boost.org/boost-build2/doc/html/bbv2/advanced/builtins/features.html
Thank you Volodya. Two suggestions: 1. The above page does not give the default values of the features. This should be added. 2. I think the documentation of how to build Boost should be made more user-friendly. There is a gap between the Getting Started Guide and the Reference Manual that should be bridged. What is needed I think, is to expand the Getting Started Guide, and describe, with plenty of examples, how to make simple customizations of the build. Right now the Getting Started Guide only describes how to do a default build. --Johan
Johan Råde wrote:
Vladimir Prus wrote:
Johan Råde wrote:
Question 1: How do I specify that the build should use a dynamic CRT?
In general, see answer to question 2. But dynamic CRT is used by default, anyway.
Question 2: Where do I find the answers to questions such a Question 1? The get started guide contains to little info, the reference manual too much.
In Boost.Build documentation. Namely: http://boost.org/boost-build2/doc/html/bbv2/advanced/builtins/features.html
Thank you Volodya.
Two suggestions:
1. The above page does not give the default values of the features. This should be added.
2. I think the documentation of how to build Boost should be made more user-friendly. There is a gap between the Getting Started Guide and the Reference Manual that should be bridged. What is needed I think, is to expand the Getting Started Guide, and describe, with plenty of examples, how to make simple customizations of the build. Right now the Getting Started Guide only describes how to do a default build.
I don't think that adding that to Getting Started is necessary. Instead, it should say have a link to a page describing general Boost.Build command line syntax, which in turn can list a few common features. There are some cleanups in getting started that I was meaning to suggest, but I need to think more about those. - Volodya
Vladimir Prus wrote:
Johan Råde wrote:
Vladimir Prus wrote:
http://boost.org/boost-build2/doc/html/bbv2/advanced/builtins/features.html
Two suggestions:
1. The above page does not give the default values of the features. This should be added.
2. I think the documentation of how to build Boost should be made more user-friendly. There is a gap between the Getting Started Guide and the Reference Manual that should be bridged. What is needed I think, is to expand the Getting Started Guide, and describe, with plenty of examples, how to make simple customizations of the build. Right now the Getting Started Guide only describes how to do a default build.
I don't think that adding that to Getting Started is necessary. Instead, it should say have a link to a page describing general Boost.Build command line syntax, which in turn can list a few common features.
Great idea! --Johan
Better not, that just wastes energy building zillion variants when you only need one. Instead, request the specific variant you want, like:
bjam link=static threading=multi toolset=msvc-7.1
- Volodya
I built Boost using this command. I got libraries called libboost_serialization-vc71-mt-1_35.lib and libboost_serialization-vc71-mt.lib that seem to be identical. Is there any difference? If not, why are both created? --Johan
one has version number attached to it and one does not.
In msvc environment where auto linking is issued boost_auto_link_nomangled
would select the one without version number.
On Wed, Feb 20, 2008 at 1:45 PM, Johan Råde
Better not, that just wastes energy building zillion variants when you only need one. Instead, request the specific variant you want, like:
bjam link=static threading=multi toolset=msvc-7.1
- Volodya
I built Boost using this command. I got libraries called
libboost_serialization-vc71-mt-1_35.lib
and
libboost_serialization-vc71-mt.lib
that seem to be identical. Is there any difference? If not, why are both created?
--Johan
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (4)
-
chun ping wang -
Johan Råde -
Steven Watanabe -
Vladimir Prus