Hey All, I'm trying to run a plone-ish buildout on Windows for a customer, currently getting this: creating zope.proxy copying zope/proxy\proxy.h -> zope.proxy error: Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing "-c mingw32" to setup.py. While: Installing zope2. Do binary eggs exist for zope.proxy and friends? If not, how do I build 'em and upload them for others to use? If they do exist, how do I get buildout to use them rather than trying to build from source on my system? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer, currently getting this:
creating zope.proxy copying zope/proxy\proxy.h -> zope.proxy error: Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing "-c mingw32" to setup.py. While: Installing zope2.
Do binary eggs exist for zope.proxy and friends?
This isn't a matter of a binary zope.proxy egg. If you look at the 'zope2' part of your buildout.cfg, you'll see it's actually trying to compile Zope 2 itself (which happens to contain the zope.proxy package as part of the Zope 3 libraries that it ships with). What you want to do on Windows is install Zope 2 manually using the installers, then edit buildout.cfg to NOT build Zope 2, but to refer to the installation location, e.g.: [zope2] location = C:\Path\to\my\zope2 # nothing else here, also remove 'zope2' from buildout:parts [instance] ... # stays the same: zope2-location = ${zope2:location} ...
Depending on how 'plone-ish' your buildout is, you can start from the newly-created, experimental buildout-based Plone Installer for Windows: https://launchpad.net/plone/3.1/3.1.2/ -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Hey Sidnei, Sidnei da Silva wrote:
Depending on how 'plone-ish' your buildout is, you can start from the newly-created, experimental buildout-based Plone Installer for Windows:
So how does this work? Where's the buildout.cfg that gets used and what recipes have you created/tweaked to make this happen? Also, related, would you be up for building binary windows eggs for the zope 3 components for both python 2.4 and python 2.5? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Sat, Jun 21, 2008 at 3:16 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Hey Sidnei,
Sidnei da Silva wrote:
Depending on how 'plone-ish' your buildout is, you can start from the newly-created, experimental buildout-based Plone Installer for Windows:
So how does this work?
There are some notes here: https://svn.plone.org/svn/plone/Installers/Windows/trunk/NOTES.txt
Where's the buildout.cfg that gets used and what recipes have you created/tweaked to make this happen?
This one is used to pre-build everything, and then we run Inno Setup to build the installer: https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/installer.... After install, we run bootstrap and buildout with this config file. All eggs will be in buildout-cache at that point: https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/buildout.c...
Also, related, would you be up for building binary windows eggs for the zope 3 components for both python 2.4 and python 2.5?
No. :) But I believe Jim volunteered. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Sidnei da Silva wrote:
This one is used to pre-build everything, and then we run Inno Setup to build the installer:
https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/installer....
Which buildout.cfg is this extending?
Also, related, would you be up for building binary windows eggs for the zope 3 components for both python 2.4 and python 2.5?
No. :) But I believe Jim volunteered.
Hmm. Jim, is this true? Is there anything I can do to help? (I doubt it, since I don't have VC++ or access to it anymore..) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On 6/23/08, Chris Withers <chris@simplistix.co.uk> wrote:
Sidnei da Silva wrote:
This one is used to pre-build everything, and then we run Inno Setup to build the installer:
https://svn.plone.org/svn/plone/Installers/Windows/trunk/buildout/installer....
Which buildout.cfg is this extending?
The one in the same directory. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Philipp von Weitershausen wrote:
This isn't a matter of a binary zope.proxy egg. If you look at the 'zope2' part of your buildout.cfg, you'll see it's actually trying to compile Zope 2 itself (which happens to contain the zope.proxy package as part of the Zope 3 libraries that it ships with).
Right, this doesn't seem sane. Is this the fault of the recipe or of buildout?
What you want to do on Windows is install Zope 2 manually using the installers, then edit buildout.cfg to NOT build Zope 2, but to refer to the installation location, e.g.:
Well, I really don't ;-) I want buildout to get binary eggs on windows or (and I know I'm asking a lot here) to get a binary Zope 2 if it needs one. I'm still hazy on what the problem is... Will buildout use binary eggs if they're available? (given that it's Windows where this is particularly important...) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
El 21 Jun 2008, a las 20:15 , Chris Withers escribió:
Philipp von Weitershausen wrote:
This isn't a matter of a binary zope.proxy egg. If you look at the 'zope2' part of your buildout.cfg, you'll see it's actually trying to compile Zope 2 itself (which happens to contain the zope.proxy package as part of the Zope 3 libraries that it ships with).
Right, this doesn't seem sane.
Is this the fault of the recipe or of buildout?
zc.buildout is a generic deployment tool. It's not related to Zope in any specific way (other than that it shares a couple of contributors). You can think of zc.buildout as 'make'. It just does what you tell it to do. buildout.cfg is the zc.buildout's "Makefile". As I said, if you look at *your* specific buildout.cfg, you'll see that it tells zc.buildout to compile Zope 2. This is not a faulty zc.buildout presetting (because zc.buildout is a generic tool).
What you want to do on Windows is install Zope 2 manually using the installers, then edit buildout.cfg to NOT build Zope 2, but to refer to the installation location, e.g.:
Well, I really don't ;-) I want buildout to get binary eggs on windows
Zope2 isn't eggified yet, so it can't be installed as eggs.
or (and I know I'm asking a lot here) to get a binary Zope 2 if it needs one.
Then you want to a) either write a recipe that does just that b) or extend the plone.recipe.zope2install recipe to get the binary Zope installer and execute it (if that's even possible) on Windows, rather than trying to get the source tarball and compile it (this would still be the default for Unixy platforms). Option b) is probably preferred because then you can share the same buildout.cfg between different platforms.
I'm still hazy on what the problem is... Will buildout use binary eggs if they're available? (given that it's Windows where this is particularly important...)
Yes, buildout just uses setuptools to fetch and install eggs. But as said, Zope 2 isn't eggified yet, so there's no point debating what kind of eggs it should have gotten. Your buildout.cfg never told it to get an egg. Your buildout.cfg tells it to compile and install Zope 2.
On Sun, Jun 22, 2008 at 1:10 PM, Philipp von Weitershausen <philipp@weitershausen.de> wrote:
b) or extend the plone.recipe.zope2install recipe to get the binary Zope installer and execute it (if that's even possible) on Windows, rather than trying to get the source tarball and compile it (this would still be the default for Unixy platforms).
Why would it not be possible? Another option would be to use some sort of 'Inno Unpacker', which I believe exists but I have not looked at. Yet another option would be to just tar up the results of running 'setup.py build-ext -i' on a extracted tarball and put it in some common location, alongside with the installer. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
Sidnei da Silva wrote:
On Sun, Jun 22, 2008 at 1:10 PM, Philipp von Weitershausen <philipp@weitershausen.de> wrote:
b) or extend the plone.recipe.zope2install recipe to get the binary Zope installer and execute it (if that's even possible) on Windows, rather than trying to get the source tarball and compile it (this would still be the default for Unixy platforms).
Why would it not be possible?
Another option would be to use some sort of 'Inno Unpacker', which I believe exists but I have not looked at.
Yet another option would be to just tar up the results of running 'setup.py build-ext -i' on a extracted tarball and put it in some common location, alongside with the installer.
...or just eggify Zope 2 into a few big eggs: - anything from Zope 3 can come from existing eggs - one big egg for the rest of Zope 2 Surely that'd do it, right? I have vague memories of someone working on this... who is it? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On 6/23/08, Chris Withers <chris@simplistix.co.uk> wrote:
Surely that'd do it, right? I have vague memories of someone working on this... who is it?
That'd be Phillip I believe. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Sidnei da Silva wrote:
On Sun, Jun 22, 2008 at 1:10 PM, Philipp von Weitershausen <philipp@weitershausen.de> wrote:
b) or extend the plone.recipe.zope2install recipe to get the binary Zope installer and execute it (if that's even possible) on Windows, rather than trying to get the source tarball and compile it (this would still be the default for Unixy platforms). Why would it not be possible?
Another option would be to use some sort of 'Inno Unpacker', which I believe exists but I have not looked at.
Yet another option would be to just tar up the results of running 'setup.py build-ext -i' on a extracted tarball and put it in some common location, alongside with the installer.
...or just eggify Zope 2 into a few big eggs:
- anything from Zope 3 can come from existing eggs - one big egg for the rest of Zope 2
Surely that'd do it, right? I have vague memories of someone working on this... who is it?
Chris McDonough did exactly that (rolle one big Zope2 egg) to support repoze.zope2: - http://dist.repoze.org/zope2/2.10/zopelib-2.10.6.0.tar.gz - http://dist.repoze.org/zope2/2.9/zopelib-2.9.8.2.tar.gz Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com 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 iD8DBQFIYGcc+gerLs4ltQ4RAjz+AJ9FakNbmaNCjxdYjKP4/tMyNc8i/gCeOagO Qy36WfgGg/4kH94phA2naRM= =2I+o -----END PGP SIGNATURE-----
Tres Seaver wrote:
Chris McDonough did exactly that (rolle one big Zope2 egg) to support repoze.zope2:
Great. So why don't we just: - get the instructions for making these somewhere in svn.zope.org - bless these as official - list them on zope.org next to the source and tarball ...and be done with it? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer, currently getting this:
creating zope.proxy copying zope/proxy\proxy.h -> zope.proxy error: Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing "-c mingw32" to setup.py. While: Installing zope2.
Do binary eggs exist for zope.proxy and friends? If not, how do I build 'em and upload them for others to use?
If they do exist, how do I get buildout to use them rather than trying to build from source on my system?
buildout will use binary eggs if they exist and match the version spec, so you may want a [version] block. However: - if you really are installing zope2, then I wonder why it's trying to download zope.proxy. This is possibly a case of egg dependencies gone wrong, and you may want to look at plone.recipe.zope2install and its "fake eggs" optoin - you probably want to do what the error message says and install mingw32. look at http://plone.org/documentation/tutorial/buildout for some instructions on how to prepare for building zope in wintendo. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
Martin Aspeli wrote:
- if you really are installing zope2, then I wonder why it's trying to download zope.proxy. This is possibly a case of egg dependencies gone wrong, and you may want to look at plone.recipe.zope2install and its "fake eggs" optoin
Hmmm :-S Can you explain this more?
- you probably want to do what the error message says and install mingw32. look at http://plone.org/documentation/tutorial/buildout for some instructions on how to prepare for building zope in wintendo.
No, I really don't. I don't what to do any C compilation on the windows boxes. I'm much more interested in fixing problems so other people on windows don't have to worry about VC++ or mingw32... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Martin Aspeli wrote:
Chris Withers wrote:
Hey All,
I'm trying to run a plone-ish buildout on Windows for a customer, currently getting this:
creating zope.proxy copying zope/proxy\proxy.h -> zope.proxy error: Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing "-c mingw32" to setup.py. While: Installing zope2.
Do binary eggs exist for zope.proxy and friends? If not, how do I build 'em and upload them for others to use?
If they do exist, how do I get buildout to use them rather than trying to build from source on my system?
buildout will use binary eggs if they exist and match the version spec, so you may want a [version] block. However:
- if you really are installing zope2, then I wonder why it's trying to download zope.proxy.
It's not, it's just compiling Zope 2 which contains zope.proxy. From my initial reply to Chris: This isn't a matter of a binary zope.proxy egg. If you look at the 'zope2' part of your buildout.cfg, you'll see it's actually trying to compile Zope 2 itself (which happens to contain the zope.proxy package as part of the Zope 3 libraries that it ships with).
participants (5)
-
Chris Withers -
Martin Aspeli -
Philipp von Weitershausen -
Sidnei da Silva -
Tres Seaver