Andi Vajda wrote:
>
> On Mar 20, 2010, at 18:41, Bill Janssen wrote:
>
> > Andi,
> >
> > Do you run what's called these days a continuous integration server?
> > We
> > use Hudson to continuously test UpLib, and find it very handy. I
> > presume
> > the ASF has such a setup somewhere. Since
On Mar 20, 2010, at 18:41, Bill Janssen wrote:
Andi,
Do you run what's called these days a continuous integration
server? We
use Hudson to continuously test UpLib, and find it very handy. I
presume
the ASF has such a setup somewhere. Since you've already got a set of
tests for pylucen
On Fri, 19 Mar 2010, Bill Janssen wrote:
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 'm
On Fri, 19 Mar 2010, Bill Janssen wrote:
Bill Janssen wrote:
But that just gives you "jcc/jcc.lib". It's the path that's interesting.
Andi, why are you putting it in the "jcc" subdirectory? Shouldn't it be
in the same place the jcc.dll file is? I see that the generated code for
jcc thin
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'
> >
Bill Janssen wrote:
> Bill Janssen wrote:
>
> > I see some code in distutils.cygwinccompiler that seems to point the
> > way. In the twisted world of Distutils/Setuptools, the way you address
> > issues like this is to generate a subclass of, in this case,
> > distutils.cygwincompiler.Mingw32C
Bill Janssen wrote:
> I see some code in distutils.cygwinccompiler that seems to point the
> way. In the twisted world of Distutils/Setuptools, the way you address
> issues like this is to generate a subclass of, in this case,
> distutils.cygwincompiler.Mingw32CCompiler, and then monkeypatch
> d
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
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
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
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
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
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
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
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
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
Hmmm, setuptools doesn't seem to know to automatically build the jcc.lib
file when using mingw32.
Bill
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
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
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
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
21 matches
Mail list logo
