Re: Proposal: buildout-based Plone Installer for Windows (PLIP #227)
Laurence Rowe <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel,gmane.comp.web.zope.plone.installers |
|---|---|
| Message-ID | <[email protected]> |
Tarek Ziade wrote: > 2008/3/17, Laurence Rowe <[email protected] <mailto:[email protected]>>: <snip /> > > > Will normal win32 python extensions compiled against the standard > windows python continue to function if we use Mingw? > > > Mingw will just let you compile source code to produce binaries, > so existing binaries should work fine. Hooking Mingw to distutils > is just fully enabling the "bdist" and "bdist_egg" commands that > would otherwise fail if a C file has to be compiled (like in some zope > packages) > > On Windows I want to continue to be able to install python-ldap, > database adapters, etc from their pre-built exe installer packages. > > > I guess it is just a matter of pointing the right Python, and iirc a list of > installed Python are displayed when you launch such an installer. > > As long as the one used for the buildout is registered in the windows > registery, it should be fine. > Will we still get the standard python.org built python in this scenario, or a custom built one? Would it matter? (as far as extensions are concerned) Larence ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/