Re: JCC 2.5.1 tarball broken

On Thu, Mar 18, 2010 at 2:34 PM, Andi Vajda wrote: > Indeed, the tar archive for JCC 2.5.1 on pypi - as produced by setup.py > sdist - was woefully incomplete. I can reproduce the problem but only on > this branch. This is rather strange. On trunk, sdist produces a correct > archive. > > Not havin

Re: building pylucene with mingw

On Mar 18, 2010, at 18:18, Bill Janssen wrote: Andi Vajda wrote: On Thu, 18 Mar 2010, Bill Janssen wrote: Andi Vajda wrote: If you don't, then just kwds["extra_link_args"] = lflags is done. I've still got to manually copy the .lib file in order to build PyLucene, but otherwise it s

Re: building pylucene with mingw

Andi Vajda wrote: > > On Thu, 18 Mar 2010, Bill Janssen wrote: > > > Andi Vajda wrote: > > > If you don't, then just kwds["extra_link_args"] = lflags is done. > >> > >>> I've still got to manually copy the .lib file in order to build > >>> PyLucene, but otherwise it seems to work. I'm wo

Re: building pylucene with mingw

On Thu, 18 Mar 2010, Bill Janssen wrote: Andi Vajda wrote: If you don't, then just kwds["extra_link_args"] = lflags is done. I've still got to manually copy the .lib file in order to build PyLucene, but otherwise it seems to work. I'm working on getting the .lib file automatically in the

Re: building pylucene with mingw

Andi Vajda wrote: > >> If you don't, then just kwds["extra_link_args"] = lflags is done. > > > I've still got to manually copy the .lib file in order to build > > PyLucene, but otherwise it seems to work. I'm working on getting the > > .lib file automatically in the right place. > > Yes, that's

Re: building pylucene with mingw

On Thu, 18 Mar 2010, Bill Janssen wrote: Andi Vajda wrote: On Thu, 18 Mar 2010, Bill Janssen wrote: Hmmm, setuptools doesn't seem to know to automatically build the jcc.lib file when using mingw32. You might need to change the platform test there to include the 'mingw32' value or add th

Re: building pylucene with mingw

Andi Vajda wrote: > > On Thu, 18 Mar 2010, Bill Janssen wrote: > > > Hmmm, setuptools doesn't seem to know to automatically build the jcc.lib > > file when using mingw32. > > You might need to change the platform test there to include the 'mingw32' > value or add the specific code to do this

Re: building pylucene with mingw

On Thu, 18 Mar 2010, Bill Janssen wrote: Hmmm, setuptools doesn't seem to know to automatically build the jcc.lib file when using mingw32. You might need to change the platform test there to include the 'mingw32' value or add the specific code to do this next to the 'win32' case. If you do

Re: updated setup.py for building JCC on Win32 with MinGW

On Thu, 18 Mar 2010, Bill Janssen wrote: Andi, attached please find a copy of jcc/setup.py with the following modifications: 1. On Windows, look in the registry to find out where the Java JDK is installed, instead of hard-coding a probably-bogus path. 2. Added a branch for "mingw32", whi

Re: building pylucene with mingw

On Thu, 18 Mar 2010, Bill Janssen wrote: Andi Vajda wrote: On Thu, 18 Mar 2010, Bill Janssen wrote: Ah! "--compiler mingw32", instead of "--compiler=mingw32". Great, thanks. This is all coming back to me (slowly)... I think this is something else that JCC should remember and apply aut

Re: building pylucene with mingw

Andi Vajda wrote: > > On Thu, 18 Mar 2010, Bill Janssen wrote: > > > Ah! "--compiler mingw32", instead of "--compiler=mingw32". > > > > Great, thanks. This is all coming back to me (slowly)... > > > > I think this is something else that JCC should remember and apply > > automatically. What d

Re: building pylucene with mingw

Hmmm, setuptools doesn't seem to know to automatically build the jcc.lib file when using mingw32. Bill

Re: building pylucene with mingw

On Thu, 18 Mar 2010, Bill Janssen wrote: Ah! "--compiler mingw32", instead of "--compiler=mingw32". Great, thanks. This is all coming back to me (slowly)... I think this is something else that JCC should remember and apply automatically. What do you think? Remember how ? from what ? You

Re: JCC 2.5.1 tarball broken

On Mon, 8 Mar 2010, Ludovico Cavedon wrote: Hi Andi, looks like the latest tarball for JCC (JCC-2.5.1.tar.gz) uploaded on [1] is broken, i.e. there are some files missing: -DESCRIPTION -CHANGES -all (or at least most) .h files [1] http://pypi.python.org/pypi/JCC/ Indeed, the tar archive for

Re: building pylucene with mingw

Ah! "--compiler mingw32", instead of "--compiler=mingw32". Great, thanks. This is all coming back to me (slowly)... I think this is something else that JCC should remember and apply automatically. What do you think? Suppose I build a Windows installer for JCC with mingw32. Should that work w

Re: building pylucene with mingw

On Thu, 18 Mar 2010, Bill Janssen wrote: OK, now I'm stymied by PyLucene itself. /c/Python26/python.exe -m jcc.__main__ --shared ... --build needs to know that we're using the mingw32 compiler. It doesn't seem to remember it, which I guess is the right solution, so I wind up with the same p

building pylucene with mingw

OK, now I'm stymied by PyLucene itself. /c/Python26/python.exe -m jcc.__main__ --shared ... --build needs to know that we're using the mingw32 compiler. It doesn't seem to remember it, which I guess is the right solution, so I wind up with the same problem: error: Unable to find vcvarsall

building JCC with MinGW, the command line

One other gotcha I should note. We knew this before, but it's good to have it recorded somewhere. When building with mingw32, you need to specify the compiler: $ python setup.py build --compiler=mingw32 But then when you go to make a binary: $ python setup.py bdist --formats=wininst you w

Re: PyLucene 2.9.2 on Windows XP with gcc 3.4.5

Yep, but that's what I have when I install MinGW and msys on a bare machine. Conservative folks, I guess. I agree, something in the 4.x line is warranted. Bill > On Thu, 18 Mar 2010, Bill Janssen wrote: > > > I'm trying to get JCC built on Win XP with latest mingw tools, which is > > gcc 3.4.

updated setup.py for building JCC on Win32 with MinGW

Andi, attached please find a copy of jcc/setup.py with the following modifications: 1. On Windows, look in the registry to find out where the Java JDK is installed, instead of hard-coding a probably-bogus path. 2. Added a branch for "mingw32", which is triggered if "--compiler=mingw32"

Re: PyLucene 2.9.2 on Windows XP with gcc 3.4.5

Upgrading gcc from the default 3.4.5 to the available 4.4.0 fixed this problem. Andi, could you add a note to the JCC build notes about what the minimum capabilities needed are? And if you could figure out the minimum version of GCC, that would probably help people, too. Bill Bill Janssen wrot

Re: PyLucene 2.9.2 on Windows XP with gcc 3.4.5

On Thu, 18 Mar 2010, Bill Janssen wrote: I'm trying to get JCC built on Win XP with latest mingw tools, which is gcc 3.4.5. I would sincerely hope that there is something more recent for mingw, based on gcc 4.x. If not, then it's time to move on to a different compiler. The 3.4.x series is

PyLucene 2.9.2 on Windows XP with gcc 3.4.5

I'm trying to get JCC built on Win XP with latest mingw tools, which is gcc 3.4.5. Here's the latest issue. Looks like a C++ issue. error: base `t_jarray<_jobject*>' with only non-default constructor in class without a constructor Bill $ python setup.py build --compiler=mingw32 running build

Re: PyLucene 2.9.2 on Windows XP

My bad. Saying $ python setup.py build --compiler=mingw32 fixes this problem. Bill > I'm trying to build PyLucene 2.9.2 on Windows XP with MinGW and msys, > using Java 1.6.0_18 SE and Python 2.6.4, without setuptools. I unpacked > the sources, and tried building JCC: > > $ python setup.py bu

PyLucene 2.9.2 on Windows XP

I'm trying to build PyLucene 2.9.2 on Windows XP with MinGW and msys, using Java 1.6.0_18 SE and Python 2.6.4, without setuptools. I unpacked the sources, and tried building JCC: $ python setup.py build running build running build_py creating build creating build\lib.win32-2.6 creating build\lib.