[Zope3-dev] Re: RFC: zopeproject
On 20 Jul 2007, at 01:17 , Hanno Schlichting wrote: I've heard that mingw can substitute, but I've never succeeded in configuring it. Have you seen my instructions for a Plone 3.0 buildout at http://svn.plone.org/svn/plone/ploneout/trunk/WINDOWS.txt ? This is the most reliable and easiest way I could find to compile C extensions on Windows without having to have any special M$ compiler. Thanks for pointing me to this. I finally took a look today and wrote down the jist of this howto: http://www.z3lab.org/sections/blogs/philipp-weitershausen/ 2007_07_26_cheap-binary-windows ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: zopeproject
Hi again. Hanno Schlichting wrote: > Philipp von Weitershausen wrote: >> I wonder, if done correctly (and I believe some people, e.g. Andreas >> Jung, have managed to get mingw to build binary eggs for them), are >> mingw-based eggs any worse than Visual C ones? > > A few years ago, MinGW (the native port is still based on GCC 3.4) > compiled C extensions were a bit slower than those compiled with Visual > C. But I haven't tried this in recent years. > > My knowledge of C compilation is too limited to judge if there are some > hidden pitfalls here, though. In order to let some people judge the result of eggs built based on my howto I made one example egg for zope.interface 3.4.0. The egg is available from http://www.hannosch.de/zope.interface-3.4.0-py2.4-win32.egg The relevant log from the bdist_egg looks like this: running build_ext building '_zope_interface_coptimizations' extension creating build\temp.win32-2.4 creating build\temp.win32-2.4\Release creating build\temp.win32-2.4\Release\src creating build\temp.win32-2.4\Release\src\zope creating build\temp.win32-2.4\Release\src\zope\interface C:\MinGW\bin\gcc.exe -mno-cygwin -mdll -O -Wall -IC:\Python24\include -IC:\Python24\PC -c src\zope\interface\_zope_interface_coptimizations.c -o build\temp.win32-2.4\Release\src\zope\interface\_zope_interface_coptimizations.o writing build\temp.win32-2.4\Release\src\zope\interface\_zope_interface_coptimizations.def C:\MinGW\bin\gcc.exe -mno-cygwin -shared -s build\temp.win32-2.4\Release\src\zope\interface\_zope_interface_coptimizations.o build\temp.win32-2.4\Release\src\zope\interface\_zope_interface_coptimizations.def -LC:\Python24\libs -LC:\Python24\PCBuild -lpython24 -lmsvcr71 -o build\lib.win32-2.4\zope\interface\_zope_interface_coptimizations.pyd Python is version 2.4.4, GCC is 3.4.2 (mingw-special). If someone tells me, that the eggs I generate this way are valid and of some use, I'm happy to help to build some more ;) Hanno ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: zopeproject
Hi,
Philipp von Weitershausen wrote:
> On 18 Jul 2007, at 19:25 , Kent Tenney wrote:
>> on my W2K machine
>>> zopeproject MyZopeProject
>>
>> fails because I don't have Visual Studio installed and it wants
>> to compile extensions for ZODB
>
> Right. Something seems to depend on ZODB 3.9.0-xyz now and we have no
> binary for that (yet). Sadly enough, I recently asked Jim to make
> Windows eggs and they've all become useless because at least half of the
> packages now have newer releases (which buildout insists on using).
>
>> I've heard that mingw can substitute, but I've never succeeded in
>> configuring it.
Have you seen my instructions for a Plone 3.0 buildout at
http://svn.plone.org/svn/plone/ploneout/trunk/WINDOWS.txt ? This is the
most reliable and easiest way I could find to compile C extensions on
Windows without having to have any special M$ compiler.
> Well, I managed to install it (you need cygwin, then install the
> gcc-mingw-core package from the 'devel' section). And with 'python
> setup.py build -c mingw32', it seems I can even build Windows eggs,
> though I can't get them to work. I get some a DLL error ("Access denied.")
>
> What's more, there seems to be now way to tell zc.buildout to pass the
> '-c mingw32' option to setup.py when building eggs.
My instructions tell you to use MinGW directly without all that Cygwin
junk which only tends to make things more complicated and often
introduces an undesired runtime dependency on Cygwin. The nice thing as
noted in my howto is that you can change a distutils option to say all
build commands should use mingw32 and so all buildout recipes will pick
this up.
> I wonder, if done correctly (and I believe some people, e.g. Andreas
> Jung, have managed to get mingw to build binary eggs for them), are
> mingw-based eggs any worse than Visual C ones?
A few years ago, MinGW (the native port is still based on GCC 3.4)
compiled C extensions were a bit slower than those compiled with Visual
C. But I haven't tried this in recent years.
My knowledge of C compilation is too limited to judge if there are some
hidden pitfalls here, though.
Hanno
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: zopeproject
On 19 Jul 2007, at 22:50 , Tres Seaver wrote: Lennart Regebro wrote: On 7/19/07, Dieter Maurer <[EMAIL PROTECTED]> wrote: But, Zope is quite easy on entry. Zope2, yes. Zope3? Not at all. Will modularizing Zope 3 make it easier for newbies? Not really, but with zopeproject or similar it shouldn't be more complicated either. In fact, the installation process might end up being simpler: Compare: wget http://www.zope.org/whatevah/Zope.tgz tar xvfz thetgz ./configure make make install make instance directory With: easy_install zopeproject zopeproject directory cd directory bin/buildout Or something similar to that. Doesn't really look more complicated to me. :-) Sure, it uses paste and stuff, but you don't have to know about that to use it. I think we need to leave soem space for people who want to customize the site, without wanting to do "full-on" Zope3 package-based development. If zopeproject makes it obvious where to put "filesystem pages", people will use them, probably. I would actually like to leave the "customizeable/pluggable app" story to another project, mostly because it's a concern that's orthogonal to zopeproject. zopeproject is actually general enough (or at least it tries to be) so that it can be used to bootstrap applications that build on top of Zope. Grok is a good example, grokproject uses zopeproject under the hood. (Grok, in a way, makes things a lot easier for the "middleclass programmer" anyway, perhaps enough for people to feel comfortable with it as a means for customizing existing apps, e.g. Plone) ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: RFC: zopeproject
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lennart Regebro wrote: > On 7/19/07, Dieter Maurer <[EMAIL PROTECTED]> wrote: >> But, Zope is quite easy on entry. > > Zope2, yes. > Zope3? Not at all. > > Will modularizing Zope 3 make it easier for newbies? Not really, but > with zopeproject or similar it shouldn't be more complicated either. > In fact, the installation process might end up being simpler: > > Compare: > > wget http://www.zope.org/whatevah/Zope.tgz > tar xvfz thetgz > ./configure > make > make install > make instance directory > > With: > > easy_install zopeproject > zopeproject directory > cd directory > bin/buildout > > Or something similar to that. Doesn't really look more complicated to me. :-) > Sure, it uses paste and stuff, but you don't have to know about that to use > it. I think we need to leave soem space for people who want to customize the site, without wanting to do "full-on" Zope3 package-based development. If zopeproject makes it obvious where to put "filesystem pages", people will use them, probably. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGn86a+gerLs4ltQ4RAhhaAKCKHbmXXHyYHRrLfmNwSntE+sxrOwCeI0Mq zbxxqSUrW10QZEsfSy0/pts= =ZHFW -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
