[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-24 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: I tried to use _CRT_NOFORCE_MANIFEST but i couldn't get it working. There're some infos about this approach at http://blog.m-ri.de/index.php/2008/05/06/hotfix-fuer-usemsprivateassembliesh-und-vc-2008/ , but even with the menti

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-22 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: .. erm, the nmake line in Tools\buildbot\external.bat and Tools/buildbot/external-amd64.bat ;) ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-22 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: Skipping the mt.exe call seems fine to me, but there's another solution which might be better: The automatic manifest binding comes from a "#pragma comment(linker,"/manifestdependency:" directive in crtdefs.h. That

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-20 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: > For some reason, the linker *does* generate manifest files for all the .pyds when I try it out. Should that worry me? When I delete them, it still can import them just fine. Hm, works for me. I am using MS SDK v6.1 and PCbuild/

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-16 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: To my surprise there indeed is a vista SP1 box in our test farm. We tested my patch on the following windows machines (each without an installed CRT redist): - xp SP2 and SP3 - xp64 SP2 - server 2003 R2 SP1 - vista with and witho

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-14 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: Ok, point taken, so lets aim at v2.6. Should i open a new issue then? Attached you'll find a new diff against v2.6. This time pyd_d.vsprops gets patched too and the linker doesn't even generate a .manifest file. So no, the *.

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-14 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: Yes, i know that v2.5 doesn't officially support MSVC9. But the same problem applies to MSVC8 and its CRT. But in contrast to MSVC9, the CRT8 redist is installed on almost every machine, because alot of software installs it. But that

[issue2563] embed manifest in windows extensions

2008-10-14 Thread Andre Heider
Andre Heider <[EMAIL PROTECTED]> added the comment: Note that this patch will break the loading of compiled modules on machines without the MS CRT redistributable installed. See Issue 4120 -- nosy: +aheider ___ Python tracker <[EMAIL

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-14 Thread Andre Heider
New submission from Andre Heider <[EMAIL PROTECTED]>: The MSVC build process currently embeds the .manifest file, which is generated by the MS linker, in the following files: - python.exe - pythonXY.dll - *.pyd The latter is problematic on machines without the MS CRT redistributable ins