boost_1_31_0 documentation - "Getting Started"
First the nit - The examples for running bjam include the arguments in double quotes as in: bjam "-sTOOLS=gcc" install Being bjam and generally makefile(and generally command line) impaired I tried: bjam "-sTOOLS=VC71" "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7" Which results in: VC71-tools.jam: No such file or directory C:\boost\boost_1_31_0\tools/build/v1\allyourbase.jam:630: in C++ rule C++-action unknown in module C:\boost\boost_1_31_0\tools/build/v1\allyourbase.jam:1097: in Object C:\boost\boost_1_31_0\tools/build/v1\allyourbase.jam:1162: in Objects C:\boost\boost_1_31_0\tools/build/v1\boost-base.jam:130: in dll-files C:\boost\boost_1_31_0\tools/build/v1\boost-base.jam:1934: in subvariant-target C:\boost\boost_1_31_0\tools/build/v1\boost-base.jam:2361: in stage Jamfile:144: in load-jamfiles C:\boost\boost_1_31_0\tools\build\v1\bootstrap.jam:15: in boost-build C:\boost\boost_1_31_0\boost-build.jam:16: in module scope Of course the following works great! bjam -sTOOLS=VC71 -sVC71_ROOT="C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7" So I'm not sure of the purpose of the "" in the documentation, but they are misleading, at least to me. The Praise - Awesome improvement in the completeness and organization of the built libs and dlls! Thanks, Jeff
"Jeff Flinn"
First the nit -
The examples for running bjam include the arguments in double quotes as in:
bjam "-sTOOLS=gcc" install
Being bjam and generally makefile(and generally command line) impaired I tried:
bjam "-sTOOLS=VC71" "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7"
Which results in:
VC71-tools.jam: No such file or directory
That's because there's no "VC71" toolset. What made you think there was?
C:\boost\boost_1_31_0\tools/build/v1\allyourbase.jam:630: in C++ rule C++-action unknown in module C:\boost\boost_1_31_0\tools/build/v1\allyourbase.jam:1097: in Object C:\boost\boost_1_31_0\tools/build/v1\allyourbase.jam:1162: in Objects C:\boost\boost_1_31_0\tools/build/v1\boost-base.jam:130: in dll-files C:\boost\boost_1_31_0\tools/build/v1\boost-base.jam:1934: in subvariant-target C:\boost\boost_1_31_0\tools/build/v1\boost-base.jam:2361: in stage Jamfile:144: in load-jamfiles C:\boost\boost_1_31_0\tools\build\v1\bootstrap.jam:15: in boost-build C:\boost\boost_1_31_0\boost-build.jam:16: in module scope
Of course the following works great!
bjam -sTOOLS=VC71 -sVC71_ROOT="C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7"
Sorry, but I have a hard time believing that. We don't have a "VC71" toolset, so the above invocation should cause an error.
So I'm not sure of the purpose of the "" in the documentation, but they are misleading, at least to me.
They work for me.
The Praise -
Awesome improvement in the completeness and organization of the built libs and dlls!
Credit to Rene Rivera. -- Dave Abrahams Boost Consulting www.boost-consulting.com
"David Abrahams"
"Jeff Flinn"
writes:
[snip]
bjam -sTOOLS=VC71 -sVC71_ROOT="C:\Program Files\Microsoft Visual Studio
.NET
2003\Vc7"
Sorry, but I have a hard time believing that. We don't have a "VC71" toolset, so the above invocation should cause an error.
That was a typo in transcribing to the email, the exact command cut & pasted from the command prompt window that worked was: bjam -sTOOLS=VC7.1 -sVC71_ROOT="C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7"
So I'm not sure of the purpose of the "" in the documentation, but they
are
misleading, at least to me.
They work for me.
The Praise -
Awesome improvement in the completeness and organization of the built
Aah, I see now it wasn't the "" that was the problem it was the missing '.' in: bjam "-sTOOLS=VC71" "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7" Sorry for jumping to conclusions. Out of curiosity, why then the inconsistency between VC7.1 tool and VC71_ROOT? libs
and dlls!
Credit to Rene Rivera.
Definitely! I see I can have both VC7.1 and VC6 builds coexist, great! Thanks again, Jeff F
participants (2)
-
David Abrahams
-
Jeff Flinn