Re: [Boost-build] msvc 64-bit test targets vs. maifest files

Subject: Re: [Boost-build] msvc 64-bit test targets vs. maifest files
From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-11-02 01:16:28

On Sunday 26 October 2008 00:33:35 Mat Marcus wrote:

> 	INFO: Reference:
> Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
> INFO: Resolving reference
> Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
> 	INFO: Resolving reference for ProcessorArchitecture amd64.
> 		INFO: Resolving reference for culture Neutral.
> 			INFO: Applying Binding Policy.
> 				INFO: No publisher policy found.
> 				INFO: No binding policy redirect found.
> 			INFO: Begin assembly probing.
> 				INFO: Did not find the assembly in WinSxS.

and earlier:

> The names of the actual DLLs in the manifest are:
> msvcr90d.dll
> msvcp90d.dll
> msvcm90d.dll
>
> These don't appear to be located in my PATH. They live in the
> nonredistributable dir, under the Dev Studio hierarchy, and they also
> seem to reside under:
>
> C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21
>022.8_none_96748342450f6aa2

Mat and I had talked about this offlist (we just forgot to CC the list), and the
conclusion is this:

1. We've no idea why the CRT in winsxs is not found, despite having exactly the requested
public token and version. I don't know what this 'none_96748342450f6aa2' prefix is supposed
to mean and how it could affect things.

2. It's not a Boost.Build problem. If one creates a 64-bit console project in IDE, with otherwise
default settings, it fails to run.

3. The only known fix is to reinstall Visual Studio -- which fixed the problem for Mat.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2