[pylucene-dev] building a PyLucene binary release for Windows

[Andi Vajda]

On Fri, 28 Mar 2008, Bill Janssen wrote:

>>> I think the right way to do this is to ask distutils/setuptools to do it for
>>> us. I should add a few other flags to jcc, say --bdist and --sdist, to do
>>> this.
>>
>> I added support for using --bdist with JCC. See JCC's README [1] for more
>> information about this new flag.
>
> Something else has changed.  I can no longer install JCC with mingw32.
> I can do the
>
>   python setup.py build --compiler=mingw32

This only builds JCC with mingw32.

> step fine, and it seems to build the .pyd file just fine, but now when
> I try to install it, I get
>
> $ python setup.py install
> running install
> running build
> running build_py
> copying jcc\config.py -> build\lib.win32-2.5\jcc
> running build_ext
> 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.
> $
>
> And, of course, passing "-c mingw32" to setup.py results in an error.

I added support for --compiler <name> to jcc. If you pass that, I pass it on 
to setup() as an argument to the build_ext command. (see jcc's python.py).
Do you have the latest jcc from trunk ?

Andi..