Hi Marc,I am pretty sure it helped on my particular configuration.
I was trying to compile MySQL-python-1.2.2.tar.gz package from source and it
was failing in mt.exe step because the manifest file was not there.
I didn't do anything special on my machine. I have 3 versions of MSVS
installed cleanly side-by-side (which is a legit scenario): MSVS 2003, MSVS
2005, and MSVS 2008. All at the latest patch levels. No standalone
PlatformSDKs are installed.

Besides, if you just ignore the obscure blurb about /MANIFEST option being
default in MSDN, and read the descriptions of both /MANIFEST and
/MANIFESTFILE options, you would agree that it will not do any harm to be
explicit and always have /MANIFEST option passed to linker.

I'm going to do one more experiment with a different machine, this time it
will be Vista (not W7) with a similar MSVS setup. I will report my findings.

On Tue, Feb 17, 2009 at 2:08 PM, Marc-Andre Lemburg
<report@bugs.python.org>wrote:

>
> Marc-Andre Lemburg <mal@egenix.com> added the comment:
>
> On 2009-02-17 20:22, Pavel Repin wrote:
> > Pavel Repin <prepin+pythonbugs@gmail.com <prepin%2Bpythonbugs@gmail.com>>
> added the comment:
> >
> > I'd like to point out that on some configurations (at least mine), you
> > really need to specify /MANIFEST option to the linker, even though MSDN
> > documentation seems to imply that /MANIFEST behavior is ON by default.
> > My config:
> > beta version of Windows 7
> > ActivePython 2.6.1.1
> > MSVS 2008 with 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08
> > for 80x86
>
> Are you sure ?
>
> We've had such a request before and the reason for MSVC not generating
> a .manifest file was some setting the user had done on his system.
>
> FWIW: distutils generates those files just fine for me.
>
> Then again, it probably doesn't hurt just adding the option.
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue4431>
> _______________________________________
>