Re: [Plone-developers] Proposal: buildout-based Plone Installer for Windows (PLIP #227)
"Tarek Ziade" <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.installers,gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
2008/3/17, Laurence Rowe <[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? 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. (semi-related, but for that particular case, we are using a pre-build python-ldap egg that contains all ldap dlls files. -> http://release.ingeniweb.com/third-party-dist/python_ldap-2.3.1-py2.4-win32.egg It is usable directly in buildouts (python_ldap) and it prevents from having to run an extra installer) 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/ > _______________________________________________ > Plone-developers mailing list > Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/plone-developers > ------------------------------------------------------------------------- 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/ _______________________________________________ Plone-installers mailing list Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-installers