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

Subject: Re: [Boost-build] library naming under Windows 64 bit compiler
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-08-27 11:26:26

AMDG

Mike Jackson wrote:
> <snip>
>
> 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
>   

This ought to be <toolset>msvc-9.0

> <snip>
>
> ...patience...
> ...found 759 targets...
> ...updating 4 targets...
> common.copy stage\lib\libboost_thread-vc-mt-gd-1_39.lib
>
> <snip>
>
> 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".
>   

This looks like a problem with the search in the registry.
Boost.Build should be looking at
HKEY_LOCAL_MACHINE\SOFTWARE\\Microsoft\VisualStudio\9.0\Setup\VC\ProductDir
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\\Microsoft\VisualStudio\9.0\Setup\VC\ProductDir

Is either one of these correct?
If not, what is the correct registry key?

In Christ,
Steven Watanabe