Steven, many thanks. I tried your suggestion and was able to verify exactly what I needed to know. It seems "bjam -help" says -n will not execute the updating actions, but it says nothing about printing commands. I didn't cross check this with the Boost web page documentation which is in fact different (and says -n will print the commands). As for the email timestamp, blackouts from storms over the last few days, and a low battery on the box I sent the email from, apparently conspired to confuse the clock. Again, thanks for your help. Rick -----Original Message-----
From: Steven Watanabe <watanabesj@gmail.com> Sent: Mar 19, 2010 6:56 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] setup question
AMDG
Rick Boesch wrote:
Hello all -- looking for a small bit of guidance please. I'm building a 64bit Boost library from scratch. I'm fairly sure I did almost everything correctly, but would like to check one nagging detail. My system is Windows 7, Visual Studio 2005 and I'm building for 64 bit, specifically AMD64.
I believe bjam.exe built correctly because my path was set up properly for the x64 toolset and bjam.exe was deposited in the auto-generated directory BOOST_ROOT\tools\jam\src\bin.ntx86_64. To do this, I ran "build vc8" on the command line.
My question concerns the use of bjam along with the "using" instruction in the ...\V2\user-config.jam file. I set the "using" instruction to be
using msvc : 8.0 : cl : <setup-amd64>vcvarsall ;
and my command line is
bjam address-model=64 --build-dir="C:\Program Files\boost\boost_1_42_0\boost-build" --build-type=complete stage
I built two different ways:
1) In a virgin cmd window -- which is not set up for 64 bit tools by default -- I ran vcvarsall manually on the command line (with no args, I set it up to default to setting up 64 bit), which sets up my 64 bit environment and which I have echo to the screen "AMD64 env" for confirmation. I confirmed I was then defaulting to the correct "cl", etc., and then executed in BOOST_ROOT the bjam command line above. I have yet to test the output, but it seemed to work.
2) In another virgin cmd window, I cd'd to BOOST_ROOT and executed ONLY the bjam command line above. According to the documentation for the "using" instruction, the batch file vcvarsall (which is in my default PATH) is supposed to be called before any tools are used, but I never saw "AMD64 env" echoed to the screen, nor to a .log file which I piped to in order to make sure I didn't miss anything. Yet, bjam created an output tree containing various "address-model-64" directories. When I checked my PATH after the build, it did not contain the paths that vcvarsall is supposed to set up.
The environment setup the Boost.Build does is local to each command.
Question: In scenario (2) above, vcvarsall clearly did not run in my cmd session, but did bjam run it in some internally generated shell? If no, why not (did I do something incorrectly)? If yes, is this why I didn't see my echo confirmation?
You can run bjam -a -n <other options> to see the commands that Boost.Build actually runs.
So I'm wondering if I have a 64 bit build or not -- and I prefer scenario (2) to scenario (1)!
In Christ, Steven Watanabe
P.S. The timestamp on this message was 2004.