[issue1488] PCBuild9 _ssl.vcproj improperly launches build

Joseph Armbruster added the comment: Whoops. This may have been an error on my part. nt.mak I think bombed for me except it was probably due to some of my tinkering. My apologies. __ Tracker <[EMAIL PROTECTED]> ___

[issue1488] PCBuild9 _ssl.vcproj improperly launches build

Changes by Christian Heimes: -- status: pending -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue1488] PCBuild9 _ssl.vcproj improperly launches build

Christian Heimes added the comment: out32 is the correct directory. The windows version of Python is statically linked against the SSL libs. We don't want to ship yet another DLL. __ Tracker <[EMAIL PROTECTED]> __

[issue1488] PCBuild9 _ssl.vcproj improperly launches build

Joseph Armbruster added the comment: Looks like the libpaths were pointing to out32 instead of out32.dll. Although that may have been due to my switch from nt.mak to ntdll.mak. __ Tracker <[EMAIL PROTECTED]>

[issue1488] PCBuild9 _ssl.vcproj improperly launches build

Christian Heimes added the comment: I've fixed (1) and (2) in r59130. I don't understand what you mean with (3). -- resolution: -> fixed status: open -> pending __ Tracker <[EMAIL PROTECTED]> ___

[issue1488] PCBuild9 _ssl.vcproj improperly launches build

Christian Heimes added the comment: Thanks, I'll check it later. -- assignee: -> tiran keywords: +patch, py3k priority: -> normal versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> __

[issue1488] PCBuild9 _ssl.vcproj improperly launches build

New submission from Joseph Armbruster: When you attempt to build the _ssl project in release or debug you can possibly encounter errors in the following scenarios: 1) having spaces in the build path 2) if you launch the build in debug, it attempts to run build_ssl.py with the python.exe found i