Re: [Boost-build] Baffling build properties

Subject: Re: [Boost-build] Baffling build properties
From: Josh Stern (josh_at_[hidden])
Date: 2010-11-18 11:55:31

David, I have a working setup with the same boost stuff and MSVC 
compiler versions installed, so even though it is probably different 
from what you want, it may help you to debug your problem.  Here are 
some possibly relevant details:

1) My system is a 64 bit version of Windows 7.
2) The environment variable $PROCESSOR_ARCHITECTURE, which is consulted 
by the msvc.jam script, is set to AMD64 before bjam is called (more on 
other environment variables below).
3) my site-config .jam says "using msvc : 10 ; even though it is 
VisualExpress 2010
4) I have VisualExpress2008 and SDK7 also installed on the machine, 
though they should be inactive in the build
5) I launch bjam from the msys version of bash, having set the 
environment variables that are expected for 64 bit compilation in my 
".profile" file for the shell (shown below) - so when vcvarsall.bat 
tries to call the vcvars script to set 64 bit stuff in case of 
address-model=64, it silently fails, but that's okay because the vars 
are already set.   When I specify address-model=32, it resets some 
variables by calling the vcvars32.bat which is included with the 
VisualExpress2010  distribution.

Here are the rest of the possibly relevant environment variable settings:

ALLUSERSPROFILE="C:\ProgramData"
APPDATA="C:\Users\josh\AppData\Roaming"
CommonProgramFiles="C:\Program Files\Common Files"
CommonProgramW6432="C:\Program Files\Common Files"
COMPUTERNAME=ATLAS
CPU=AMD64
export PROCESSOR_ARCHITECTURE=AMD64

HOMEDRIVE=C:
HOMEPATH="\Users\josh"

Include="C:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\Include;C:\Program Files\Microsoft 
SDKs\Windows\v7.1\Include;C:\Program Files\Microsoft 
SDKs\Windows\v7.1\Include\gl;"

Lib="C:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\Lib\amd64;C:\Program Files\Microsoft SDKs\Windows\v7.1\Lib\X64;"

MSSdk="C:\Program Files\Microsoft SDKs\Windows\v7.1"

SdkSetupDir="C:\Program Files\Microsoft SDKs\Windows\v7.1\Setup"
SdkTools="C:\Program Files\Microsoft 
SDKs\Windows\v7.1\Bin\x64;C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin"

#VCINSTALLDIR="C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC"
VCINSTALLDIR="C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC"

#VCROOT="C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC"
VCROOT="C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC"

VS90COMNTOOLS="C:\Program Files (x86)\Microsoft Visual Studio 
9.0\Common7\Tools"

VS100COMNTOOLS="C:\Program Files (x86)\Microsoft Visual Studio 
10.0\Common7\Tools"

VSRegKeyPath="HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\SxS\VS7"
windir="C:\Windows"

export Lib
export Include
export MSSdk
export SdkSetupDir
export SdkTools
export VCINSTALLDIR
export VCRoot
export VS90COMNTOOLS
export VSRegKeyPath

LOCALAPPDATA="C:\Users\josh\AppData\Local"

export LOCALAPPDATA

PF86="C:\Program Files (x86)"
export PF86
BOOST="$PF86\boost\boost_1_44"
export BOOST_BUILD_PATH="$BOOST"

#MSVCP="$PF86\Microsoft Visual Studio 9.0"
MSVCP="$PF86\Microsoft Visual Studio 10.0"

SDK7="C:\Program Files\Microsoft SDKs\Windows\v7.1"

PATH="$PATH:C:\bin:$PF86\XEmacs\XEmacs-21.4.22\i586-pc-win32:$BOOST\bin:$MSVCP\VC\bin\amd64:$MSVCP\VC\vcpackages:$MSVCP\Common7\IDE:$SDK7\Bin\x64:$SDK7\Bin:$SDK7\Setup:$PF86\Mercurial:C:\Windows\system32"

export VSINSTALLDIR="$MSVCP"
export VCINSTALLDIR=$VSINSTALLDIR"\VC"

LIBPATH32="C:\lib\win32"
LIBPATH64="C:\lib\win64"
LIBPATH="$LIBPATH":"$LIBPATH64":"$LIBPATH32"

PATH="$PATH:$LIBPATH"

export PATH

On 11/17/2010 8:02 PM, David Abrahams wrote:
> The build I am running works just fine unless I add "address-model=64"
> to the command line, at which point I get:
>
>    error: link=shared together with runtime-link=static is not allowed
>    error: such property combination is either impossible
>    error: or too dangerious to be of any use
>
> and BB bails out.  What the...?  I'm just building boost's "stage"
> target.  How can I get around this problem, please!?
>