Re: [Boost-build] library naming under Windows 64 bit compiler

Subject: Re: [Boost-build] library naming under Windows 64 bit compiler
From: Mike Jackson (mike.jackson_at_[hidden])
Date: 2009-08-25 12:20:55

notice: found boost-build.jam at
C:/Users/mjackson/Workspace/boost_1_39_0/boost-build.jam
notice: loading Boost.Build from
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2
notice: Searching C:\Windows C:\Users\mjackson C:\Users\mjackson
C:\Users\mjackson\Workspace\boost_1_39_0\tools/build/v2
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/kernel
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/util
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/build
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/tools
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/contrib
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/. for
site-config configuration file site-config.jam .
notice: Loading site-config configuration file site-config.jam from
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/site-config.jam
.
notice: Searching C:\Users\mjackson C:\Users\mjackson
C:\Users\mjackson\Workspace\boost_1_39_0\tools/build/v2
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/kernel
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/util
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/build
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/tools
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/contrib
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/. for
user-config configuration file user-config.jam .
notice: Loading user-config configuration file user-config.jam from
C:/Users/mjackson/Workspace/boost_1_39_0/tools/build/v2/user-config.jam
.
notice: [cmdline-cfg] Detected command-line request for msvc: toolset=
msvc version=
notice: [cmdline-cfg] toolset msvc not previously configured;
attempting to auto-configure now
notice: will use 'cl.exe' for msvc, condition <toolset>msvc
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>/<address-model>', setup: 'call
"c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat"  >nul
'
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>/<address-model>32', setup: 'call
"c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat"  >nul
'
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>x86/<address-model>', setup: 'call
"c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat"  >nul
'
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>x86/<address-model>32', setup: 'call
"c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\vcvars32.bat"  >nul
'
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>/<address-model>64', setup: 'call
"c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat"  >nul
'
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>x86/<address-model>64', setup: 'call
"c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat"  >nul
'
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>ia64/<address-model>', setup: ''
notice: [msvc-cfg] condition:
'<toolset>msvc/<architecture>ia64/<address-model>64', setup: ''
notice: iostreams: not using zlib compression
notice: iostreams: not using zlib compression
notice: iostreams: not using bzip2 compression
notice: iostreams: not using bzip2 compression
notice: [python-cfg] Configuring python...
notice: [python-cfg] Checking interpreter command "python"...
notice: [python-cfg] running command '"python" -c "from sys import *;
print 'version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s'
% (version_info[0],version_info[1],platform,prefix,exec_prefix,executable)"
2>&1'
notice: [python-cfg] ...does not invoke a working interpreter
notice: [python-cfg] No working Python interpreter found.
notice: [python-cfg] falling back to "python"
notice: [python-cfg] Details of this Python configuration:
notice: [python-cfg]   interpreter command: "python"
notice: [python-cfg]   include path: "Include"
notice: [python-cfg]   library path: "\libs"
notice: [python-cfg]   DLL search path: "<empty>"
WARNING: No python installation configured and autoconfiguration
         failed.  See http://www.boost.org/libs/python/doc/building.html
         for configuration instructions or pass --without-python to
         suppress this message and silently skip all Boost.Python targets

Building C++ Boost.

After the build, the headers will be located at

    C:\Users\mjackson\Workspace\boost_1_39_0

The libraries will be located at

    C:\Users\mjackson\Workspace\boost_1_39_0\stage\lib

Use 'bjam install --prefix=<path>' if you wish to install headers and
libraries to a different location and remove the source tree.

...patience...
...found 759 targets...
...updating 4 targets...
common.copy stage\lib\libboost_thread-vc-mt-gd-1_39.lib
bin.v2\libs\thread\build\msvc\debug\address-model-64\link-static\threading-multi\libboost_thread-vc-mt-gd-1_39.lib
        1 file(s) copied.
ln-NT stage\lib\libboost_thread-vc-mt-gd.lib
"NT symlinks not supported yet, making copy"
Could Not Find C:\Users\mjackson\Workspace\boost_1_39_0\stage\lib\libboost_thread-vc-mt-gd.lib
        1 file(s) copied.
common.copy stage\lib\libboost_thread-vc-mt-1_39.lib
bin.v2\libs\thread\build\msvc\release\address-model-64\link-static\threading-multi\libboost_thread-vc-mt-1_39.lib
        1 file(s) copied.
ln-NT stage\lib\libboost_thread-vc-mt.lib
"NT symlinks not supported yet, making copy"
Could Not Find C:\Users\mjackson\Workspace\boost_1_39_0\stage\lib\libboost_thread-vc-mt.lib
        1 file(s) copied.
...updated 4 targets...

C:\Users\mjackson\Workspace\boost_1_39_0>bjam_x64.exe --debug-configuration --wi
th-thread variant=debug,release link=static runtime-link=shared threading=multi
address-model=64 toolset=msvc > out2.txt

I can send the entire out.txt file but it is large. This was done on a
freshly unpacked boost 1.39.tar.gz folder. The system is Windows 7 x64
Ultimate with Visual Studio 2008 Standard Edition installed (using
just defaults for the installation).

I compiled bjam separately for x64 use as the 32 bit version did not
seem to work correctly. This was also done in the "Visual Studio 2008
x64 Win64 Command Prompt".

I guess I could try with
_________________________________________________________
Mike Jackson                  mike.jackson_at_[hidden]

On Tue, Aug 25, 2009 at 1:50 AM, Vladimir Prus<ghost_at_[hidden]> wrote:
> On Monday 24 August 2009 Mike Jackson wrote:
>
>> Using VS 2008 Standard Edition and the VS x64 command prompt I
>> configured boost 1.39 using the "address-model=64" option to get 64
>> bit binaries. All seemed to work except that the naming of the
>> libraries are:
>>
>> libboost_filesystem-vc-mt-1_39.lib
>>
>> Usually I would see:
>>
>> libboost_filesystem-vc90-mt-1_39.lib  using a 32 bit command prompt
>> under VS2008 and Windows XP. What's up?
>
> Please add the --debug-configuration option, provide the exact command line
> after that addition, and the output that is produced. This should be
> enough to diagnose this.
>
> Thanks,
> Volodya
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>