Is the coredev buildout for Plone 4 supposed to work on Windows?

[Karl Johan Kleist]

Is the buildout "http://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0" supposed to work with Windows? Has anybody using Windows 7 actually made progress?

If building fails for me, should I submit a trac ticket? (No: it's not PIL that fails... )

Thanks for any clues!

[Martin Aspeli]

Karl Johan Kleist wrote:
> Is the buildout
> "http://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0"
> supposed to work with Windows? Has anybody using Windows 7 actually made
> progress?
>
> If building fails for me, should I submit a trac ticket? (No: it's not PIL
> that fails... )

If you have an error, please describe it (rather than describing what it
isn't).

Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book


_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup

[Karl Johan Kleist]

I've just been told on #zope that since the coredev Plone 4 buildout uses Zope from svn, it must be built (and not with any C compiler, but the one that built Python).

One should be able to pre-install Zope using the Windows installer, and tell buildout to use it. However, no Windows installer seems to exist for Zope 2.12:

http://www.zope.org/Products/Zope/
https://mail.zope.org/pipermail/zope-dev/2009-August/037508.html

So I will probably resort to Linux for trying out Plone 4.

Martin Aspeli wrote:

If you have an error, please describe it (rather than describing what it
isn't).

[Martin Aspeli]

Karl Johan Kleist wrote:
>
> I've just been told on #zope that since the coredev Plone 4 buildout uses
> Zope from svn, it must be built (and not with any C compiler, but the one
> that built Python).

If you look at http://plone.org/docuemtation/tutorial/buildout, it tells
you how to install mingw32 on Windows and configure it for distutils.
That should make the build work.

> One should be able to pre-install Zope using the Windows installer, and tell
> buildout to use it. However, no Windows installer seems to exist for Zope
> 2.12:

Right, not yet, I guess. But you can build Zope on Windows with the
instructions above.

> http://www.zope.org/Products/Zope/
> https://mail.zope.org/pipermail/zope-dev/2009-August/037508.html
>
> So I will probably resort to Linux for trying out Plone 4.

Or that. :)

Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book


_______________________________________________
Setup mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/setup

[Karl Johan Kleist]

Thanks Martin, your pointer set me on the track. Building Zope now works fine.

However, buildout derails shortly afterwards:

--------------------------------------------------------------------------------------
Generated script 'E:\\buildout\\plone4coredev\\bin\\mkzopeinstance'.
Generated script 'E:\\buildout\\plone4coredev\\bin\\runzope'.
  File "E:\buildout\plone4coredev\bin\mkzopeinstance.exe", line 1
SyntaxError: Non-ASCII character '\x90' in file E:\buildout\plone4coredev\bin\mkzopeinstance.exe on line 1, but no encoding declared;
see http://www.python.org/peps/pep-0263.html for details
While:
  Installing instance.

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "e:\buildout\plone4coredev\eggs\zc.buildout-1.4.1-py2.6.egg\zc\buildout\buildout.py", line 1659, in main
    getattr(buildout, command)(args)
  File "e:\buildout\plone4coredev\eggs\zc.buildout-1.4.1-py2.6.egg\zc\buildout\buildout.py", line 532, in install
    installed_files = self[part]._call(recipe.install)
  File "e:\buildout\plone4coredev\eggs\zc.buildout-1.4.1-py2.6.egg\zc\buildout\buildout.py", line 1203, in _call
    return f()
  File "e:\buildout\plone4coredev\src\plone.recipe.zope2instance\src\plone\recipe\zope2instance\__init__.py", line 88, in install
    ) == 0
AssertionError
--------------------------------------------------------------------------------------

Could the cause be, that I'm not using "setuptools" but "distribute" (distribute-0.6.6-py2.6.egg, 32 bit Python, Windows 7) ? This worked fine on Linux, but on Windows some black magic involving generated *.exe / *-script.py files seems to fail.

Martin Aspeli wrote:

If you look at http://plone.org/documentation/tutorial/buildout, it tells
you how to install mingw32 on Windows and configure it for distutils.

[Karl Johan Kleist]

No, distribute is not to blame: I get the same error when using the normal procedure with setuptools.

And I've tried using both buildout.exe and buildout-script.py (why are both provided, by the way?). Also, I've tried both the new PowerShell and the old cmd.exe console.

I guess I have to file a ticket at https://bugs.launchpad.net/collective.buildout/ ?

Karl Johan Kleist wrote:

Could the cause be, that I'm not using "setuptools" but "distribute" (distribute-0.6.6-py2.6.egg, 32 bit Python, Windows 7) ? This worked fine on Linux, but on Windows some black magic involving generated *.exe / *-script.py files seems to fail.

[Karl Johan Kleist]

I've found the solution, and filed a bug report: https://bugs.launchpad.net/collective.buildout/+bug/462731

By just changing a "0" to "1" in "plone.recipe.zope2instance\src\plone\recipe\zope2instance\__init_.py" everything now works fine.