Bugs item #1570417, was opened at 2006-10-04 05:45 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1570417&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Distutils Group: Python 2.4 >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Richard Jones (richard) Assigned to: Thomas Heller (theller) Summary: 2.4 & 2.5 can't create win installer on linux Initial Comment: With python 2.4.3 and 2.5 I can't build a Windows installer on Linux. I get the following error: Warning: Can't read registry to find the necessary compiler setting Make sure that Python modules _winreg, win32api or win32con are installed. removing 'build/bdist.linux-i686/wininst' (and everything under it) I can still create an installer with 2.3.5 ---------------------------------------------------------------------- >Comment By: Martin v. Löwis (loewis) Date: 2006-11-26 10:01 Message: Logged In: YES user_id=21627 Originator: NO Ah, right. Closing this as invalid: the message is a warning, not an error. ---------------------------------------------------------------------- Comment By: Thomas Heller (theller) Date: 2006-11-24 20:39 Message: Logged In: YES user_id=11105 Originator: NO Can this be closed, Martin? When I try 'setup.py bdist_wininst' on Linux, I get the warning but an exe is built. ---------------------------------------------------------------------- Comment By: Thomas Heller (theller) Date: 2006-10-05 21:34 Message: Logged In: YES user_id=11105 For pure distributions, bdist_wininst should create installers that are independent on the Python version. This worked up to Python 2.3, starting with 2.4 problems could arise because different MS C runtime libs are used. So, to fix this problem, even for pure distributions it should be required to specify the target-version command line switch. When building on non-windows systems, or even on Windows systems for another Python version than the one used to build the installer, bdist_wininst.py could hardcode the knowledge about Python version/MSVC version for the official python.org releases. This will fail if someone builds his own version of Python, for example 2.5 with MSVC 8. The real solution would be to avoid having wininst-XXX.exe use the C runtime library at all. OTOH, in my experience using the wrong C runtime library only has small effects - the installer would fail to show output from the pre- or post-install scripts (if they are used at all). ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2006-10-04 08:30 Message: Logged In: YES user_id=21627 The message you get is a warning only; you can ignore it. However, it still fails because it can't determine what msvcrt version the target python was built with. It needs to find that out because it needs to decide whether to use wininst-6.exe or wininst-7.1.exe. Thomas, can you think of a way to fix this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1570417&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
