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]> |
Martin Aspeli wrote: > Sidnei da Silva wrote: >> Hi Tarek, >> >> On Fri, Mar 14, 2008 at 2:50 PM, Tarek Ziade <[email protected]> wrote: >>> 1/ The pre-built story: >>> >>> I am wondering if we really need to ship prebuilt versions.. If I recall it >>> correctly, >>> a plain Plone doesn't need extra libs to be compiled, just a compiler. >> But why would you compile everything on the target system? There's no >> reason for that at all, it's just wasting resources. >> >>> And Mingw can be shipped with the installer, without having to be installed >>> on the system >>> itself. It is just a simple folder that can be linked to distutils. >> That can be done yes. > > I think it's nice if we can include a properly configured > (distutils.cfg) mingw with the Python install that comes with the > Windows installer, so that people can more easily compile future eggs. > > Having the stock eggs pre-compiled is probably sensible though. > > Martin > Will normal win32 python extensions compiled against the standard windows python continue to function if we use Mingw? On Windows I want to continue to be able to install python-ldap, database adapters, etc from their pre-built exe installer packages. Laurence ------------------------------------------------------------------------- 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/