Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-11-25 21:16, David Schnur wrote: > New submission from David Schnur <[EMAIL PROTECTED]>: > > This is my first time submitting an issue; sorry if I am doing this > wrong. While attempting to build/install PyOpenSSL on Windows / MSVC, > the mt.exe step failed because it could not find the manifest file that > it was attempting to embed in crypto.pyd. The problem was that link.exe > was not creating the manifest. > > The reason why is that distutils only passes link.exe the > /MANIFESTFILE:filename parameter. This tells it where to output the > manifest, but not to actually create the manifest (see > http://msdn.microsoft.com/en-us/library/fft52235(VS.80).aspx). You'd > think link could figure out that, if you use /MANIFESTFILE, you want a > manifest, but I guess not ;) > > My solution was to add this line to distutils/msvc9compiler.py: > > ld_args.append('/MANIFEST') > > Right beneath the existing line: > > ld_args.append('/MANIFESTFILE:' + temp_manifest) > > Hope that helps
I'm not sure whether that's necessary. We are building pyOpenSSL just fine against stock Python 2.6.0 in our distribution: http://www.egenix.com/products/python/pyOpenSSL/ and even though the command line does not include the /MANIFEST switch, the linker does builds the .manifest file just fine. OTOH, it probably doesn't hurt adding the switch :-) ---------- nosy: +lemburg _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4431> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com