Boost CVS not playing well with MSVC 8.0
Hi Everyone, I've recently just got the courage to get the CVS source from sourceforge, and I had encountered numerous problems with building/installing it, and then actually using it -- in Windows after having working with boost for quite a while now in Linux. As the post suggests, I'm using MS Visual C++ 8.0 (the free one, which comes with the Express edition of the IDE) and here are two of the problems encountered while building: 1) Python is already installed in the system (C:\Python24) but the build system still complains about it -- tried defining PYTHON_ROOT to no avail and "--with-python-root=[]" but the flag is not recognized (and turns up an error using Boost.Jam v 2). 2) Tools not explicitly defined in documentation: I had to wade through errors and complaints from Boost.Jam to find out that I needed bison,flex,m4 among other stuff. I haven't seen any documentation requiring these tools, and it would be very much appreciated if they were conveniently expressed in documentation. (more a request/observation than anything) 3) Defaults for msvc 8.0 like directory paths, etc. had to be manually defined. Though this may be addressed with Boost.Build, I still don't have enough experience with it to actually propose a fix/workaround. The Platform SDK environment vars also had to be set, which which distributed apart from the MSVC 8.0 Express toolchain -- which might become a requirement in the future, but am too much of an MS noob to start figuring this out for now. When building, there are a lot of deprecated complaints, and even template warnings. This might have something to do with the changes from 7.1 to 8.0, though they are mostly warnings than anything else. I had encountered installation and usage issues that might be specific to MSVC 8.0, and I've summarized them below: - libs build alright, and are copied to the specified location. However, when a project built using the unit_testing_framework for example is about to link to the .lib, MSVC 8.0 looks for a file named "libboost_unit_test_framework-vc80-mt-gd-1_35.lib" but only "boost_unit_test_framework-vc-gd-1_35.lib" is available. - headers don't get copied fully when installed: I had to manually copy over a lot of the preprocessor library and the mpl library into the install directory. Any tips and pointers (and other information that you think might be helpful) will be most appreciated. I still have to figure out Boost.Jam to be able to contribute to the installation and usage problems outlined above, although I hope the above report helps. NOTE: I only uncommented "using msvc ; " in user-config.jam -- please let me know if there are other things that might be helpful to make sense of the stuff posted above. Have a great day everyone, and hope this helps! -- Dean Michael C. Berris C/C++ Software Architect Orange and Bronze Software Labs http://3w-agility.blogspot.com/ http://cplusplus-soup.blogspot.com/ Mobile: +639287291459 Email: dean [at] orangeandbronze [dot] com
Dean Michael Berris wrote:
NOTE: I only uncommented "using msvc ; " in user-config.jam -- please let me know if there are other things that might be helpful to make sense of the stuff posted above.
Please mention what version of Boost in CVS you are using. Is it the HEAD or RC_1_34_0 branch? Please mention more details as to what it failed to do. Like which headers it failed to copy. I know we can likely figure out what failed ourselves but knowing ahead of time speeds up fixing the problems. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
On 6/29/06, Rene Rivera <grafikrobot@gmail.com> wrote:
Dean Michael Berris wrote:
NOTE: I only uncommented "using msvc ; " in user-config.jam -- please let me know if there are other things that might be helpful to make sense of the stuff posted above.
Please mention what version of Boost in CVS you are using. Is it the HEAD or RC_1_34_0 branch?
I did a "cvs status -l -v" and here is the output of the file named boost-build.jam in the boost root directory: File: boost-build.jam Status: Up-to-date Working revision: 1.9 Repository revision: 1.9 /cvsroot/boost/boost/boost-build.jam,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Existing Tags: RC_1_34_0 (branch: 1.9.2) merged_to_RC_1_34_0 (revision: 1.9) Version_1_33_1 (revision: 1.8) Version_1_33_1_beta (revision: 1.8) Version_1_33_0 (revision: 1.8) RC_1_33_0 (branch: 1.8.14) merged_to_RC_1_33_0 (revision: 1.8) SPIRIT_RC_1_6_2 (branch: 1.8.12) SPIRIT_RC_1_8_2 (branch: 1.8.10) SPIRIT_MINIBOOST (branch: 1.8.8) Version_1_32_0 (revision: 1.8) RC_1_32_0 (branch: 1.8.6) merged_to_RC_1_32_0 (revision: 1.8) merged_to_RC_ (revision: 1.8) function_signature_patches_1_31 (branch: 1.8.4) minmax (revision: 1.8) Version_1_31_0 (revision: 1.8) RC_1_31_0 (branch: 1.8.2) merged_to_RC_1_31_0 (revision: 1.8) Version_1_30_2 (revision: 1.5) RC_1_30_2 (revision: 1.5) Version_1_30_1 (revision: 1.5) mpl_v2_2 (branch: 1.7.2) Version_1_30_0 (revision: 1.5) merged_to_RC_1_30_0 (revision: 1.5) RC_1_30_0 (branch: 1.5.2) Version_1_29_0 (revision: 1.3) boost_python_llnl_ (revision: 1.3) RC_1_29_0 (branch: 1.3.4) python-v2-dev (branch: 1.3.2) RC_1_28_0_last_merge (revision: 1.2.2.1) Version_1_28_0 (revision: 1.2.2.1) RC_1_28_0 (branch: 1.2.2)
Please mention more details as to what it failed to do. Like which headers it failed to copy. I know we can likely figure out what failed ourselves but knowing ahead of time speeds up fixing the problems.
I had forgot the exact details, but as far as I can recall, the headers it failed to copy are in boost/mpl/aux_/config , boost/mpl/aux_/preprocessor/ , boost/mpl/aux_/preprocessed , boost/repetition/detail/msvc/for.hpp -- I can only mention these because I had only copied over what was required to build the library I am working on. Hope this helps! -- Dean Michael C. Berris C/C++ Software Architect Orange and Bronze Software Labs http://3w-agility.blogspot.com/ http://cplusplus-soup.blogspot.com/ Mobile: +639287291459 Email: dean [at] orangeandbronze [dot] com
Dean Michael Berris wrote:
On 6/29/06, Rene Rivera <grafikrobot@gmail.com> wrote:
Dean Michael Berris wrote:
NOTE: I only uncommented "using msvc ; " in user-config.jam -- please let me know if there are other things that might be helpful to make sense of the stuff posted above. Please mention what version of Boost in CVS you are using. Is it the HEAD or RC_1_34_0 branch?
I did a "cvs status -l -v" and here is the output of the file named boost-build.jam in the boost root directory:
File: boost-build.jam Status: Up-to-date
Working revision: 1.9 Repository revision: 1.9 /cvsroot/boost/boost/boost-build.jam,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none)
OK, so it's the HEAD version... Unless you have a good reason to use HEAD, for example you are testing or developing a new Boost library that won't be in 1.34.0, I would suggest switch to the RC_1_34_0 branch. It's more stable as we are devoting more testing resources to it. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
On 6/29/06, Rene Rivera <grafikrobot@gmail.com> wrote:
OK, so it's the HEAD version... Unless you have a good reason to use HEAD, for example you are testing or developing a new Boost library that won't be in 1.34.0, I would suggest switch to the RC_1_34_0 branch. It's more stable as we are devoting more testing resources to it.
Okay, sounds like good advice. I'll update if the problem exists. Thanks! (Though in another project, I use asio -- I suppose I'll use Boost CVS HEAD for that...) Is there a formal process for submitting patches? Or will attaching it to a post be alright? -- Dean Michael C. Berris C/C++ Software Architect Orange and Bronze Software Labs http://3w-agility.blogspot.com/ http://cplusplus-soup.blogspot.com/ Mobile: +639287291459 Email: dean [at] orangeandbronze [dot] com
On 6/29/06, Dean Michael Berris <mikhailberis@free.net.ph> wrote:
Okay, sounds like good advice. I'll update if the problem exists.
The problem persists in RC_1_34_0 -- the headers posted in the first message aren't being copied over to the install directory. Those that I have encountered are boost/preprocessor/repetition/detail/msvc/for.hpp and a whole bunch from boost/mpl/ -- where should I start looking for a fix? -- Dean Michael C. Berris C/C++ Software Architect Orange and Bronze Software Labs http://3w-agility.blogspot.com/ http://cplusplus-soup.blogspot.com/ Mobile: +639287291459 Email: dean [at] orangeandbronze [dot] com
On 6/29/06, Dean Michael Berris <mikhailberis@gmail.com> wrote:
On 6/29/06, Dean Michael Berris <mikhailberis@free.net.ph> wrote:
Okay, sounds like good advice. I'll update if the problem exists.
The problem persists in RC_1_34_0 -- the headers posted in the first message aren't being copied over to the install directory. Those that I have encountered are boost/preprocessor/repetition/detail/msvc/for.hpp and a whole bunch from boost/mpl/ -- where should I start looking for a fix?
It might help to mention that the headers aren't being copied over when using Boost.Build v2 (or "bjam --v2 install --prefix=..."). I hope this helps. -- Dean Michael C. Berris C/C++ Software Architect Orange and Bronze Software Labs http://3w-agility.blogspot.com/ http://cplusplus-soup.blogspot.com/ Mobile: +639287291459 Email: dean [at] orangeandbronze [dot] com
participants (3)
-
Dean Michael Berris -
Dean Michael Berris -
Rene Rivera