Boost Testing :
From: Reece Dunn (msclrhd_at_[hidden])
Date: 2005-05-25 13:27:59
David Abrahams wrote:
>"Reece Dunn" <msclrhd_at_[hidden]> writes:
> > Victor A. Wagner Jr. wrote:
> >> I don't see any change, and I don't understand this "manifest" stuff
> >> either.
> >> it almost looks like the test framework is attempting to invoke the
> >> ........manifest file directly
> > The VC8 compiler generates a .manifest file by default.
>Not according to MS. They told me the manifest gets extracted from
When the compiler sees:
in the source code, this tells VC8 to add "..." to a manifest file. For the
CRT, this is in <crtdefs.h>. There is one for ATL and MFC. These
In order to disable the manifest files, you can define _CRT_NOFORCE_MANIFEST
so the #pragma lines won't be seen by the compiler, so a manifest file
should not then be generated.
> > This is an XML file that locates the correct version of a DLL on
> > Windows XP. The XP theming support is done by comctl32.dll version 6
> > that can only be identified through a manifest. VC8 adds manifest
> > support for the Debug/Release versions of the standard library, ATL
> > and MFC DLLs.
> > I can only assume that there is a conflict somewhere when generating
> > manifest files.
>Hyah, I'd say so.
Looking at http://tinyurl.com/8yqrq, it appears that it is trying to embed
the manifest file into the exe as part of the resource data associated with
it, but for some reason is failing.
Is this a global problem (i.e. are all projects affected) in which case it
is probably a BBv1 issue. I have built projects with BBv2, so that appears
to be fine (using VC8 beta 2 - 14.00.50215.44).
In the build directory, is there the correct EXE file (because the manifest
tool is unable to find it)?
Is the configuration different in the projects that break? Do they have a
resource file? Is a manifest file supplied by that resource file?
Reece Haston Dunn
Software Engineer, Sophos
Sophos - protecting businesses against viruses and spam