Re: [boost] Embedding manifest into the regression tests (was: [testers] [log] Problems with tests)

Subject: Re: [boost] Embedding manifest into the regression tests (was: [testers] [log] Problems with tests)
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-05-13 13:50:54

On Monday 13 May 2013 16:06:01 Sergey Cheban wrote:
> 
> I've found that the same tests succeeded for the msvc-9.0 toolset. It is
> because the manifest file is generated for this toolset. I've found that
> the "C:\Program Files (x86)\Microsoft Visual Studio
> 9.0\VC\include\crtdefs.h" file contais the following:
> ===============================================
> #pragma comment(linker,"/manifestdependency:\"type='win32' "           \
>          "name='" __LIBRARIES_ASSEMBLY_NAME_PREFIX ".DebugCRT' "        \
>          "version='" _CRT_ASSEMBLY_VERSION "' "                         \
>          "processorArchitecture='x86' "                                 \
>          "publicKeyToken='" _VC_ASSEMBLY_PUBLICKEYTOKEN "'\"")
> ===============================================
> and the "C:\Program Files (x86)\Microsoft Visual Studio
> 10.0\VC\include\crtdefs.h" and "C:\Program Files (x86)\Microsoft Visual
> Studio 11.0\VC\include\crtdefs.h" contain no such code.
> 
> The bjam scripts embed the manifest into the executable if it was
> generated by the linker. And the linker generates the manifest by
> default if the /manifestdependency option was specified.
> 
> May be, it is reasonable to add the "/MANIFEST" to the linker options
> explicitly.

I know little about Windows manifests, but if I'm not mistaken, 
/manifestdependency describes the dependency to be put in the manifest and 
/MANIFEST only tells the linker to generate the .manifest file. If MSVC 10 and 
11 removed their /manifestdependency then what should be put into the 
manifest?