Re: [Boost-build] [bjam] Generating bjam.exe in the SVN Trunk

From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2008-02-05 18:42:01

   Hi Charles.

>>   That is the batch file started by build.bat to get the correct
>> environment set up for using Visual Studio tools from the command
>> line.
>>   Look into that batch file (or just run it)...
> 
> I ran it with:
> C:\Program Files\Microsoft Visual Studio 8\VC>.\vcvarsall.bat
> 
> and the response is:
> Setting environment for using Microsoft Visual Studio 2005 x86 tools.
> 
>> ...make sure it sets up the correct library search settings.

   OK, when I said that I meant 'make sure the batch file sets the 
correct settings', not Visual Studio (that one you already said has the 
correct settings :-)).

> The Include Files menu item lists
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include 
> [the location of windows.h] (and numerous others)

   This seems to be the proper one and is most likely missing from the 
environment set up by the vcvarsall.bat batch file.

> The Library Files menu item lists
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib (and 
> numerous others)

   If the previous one is missing, than most likely this one is missing 
too but you'll run into that only once you hit the linking stage. :-)

>> ...on VS7.1 the corresponding vcvars32.bat file is located
>> in %VS71COMNTOOLS%/vcvars32.bat and it sets LIB &
>> INCLUDE environment variables to be used by cl.exe.
> 
> My vcvars32.bat is empty except for the single line:
> "%VS80COMNTOOLS%vsvars32.bat"
> 
> Invoking .\vcvars32.bat produces the response:
> Setting environment for using Microsoft Visual Studio 2005 x86 tools.
> 
> jam's build.bat file still can't find windows.h.

   OK, and what settings did it configure? Did you look into the 
%VS80COMNTOOLS%vsvars32.bat file it calls?

   Either look into that file directly to see what variable it sets or 
save your environment settings ('set' command) before running the 
vcvarsall.bat/vsvars32.bat (they most likely forward to the same worker 
script) and after it and then compare them...

   Best regards,
     Jurko Gospodnetić