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 want jcc to invoke the compiler, tell it
which one via --compiler.
Suppose I build a Windows installer for JCC with mingw32. Should
that work with Visual Studio, if unpacked on a machine that doesn't
have mingw32 but does have Visual Studio? In which case the option
should stay explicit, instead of remembered, I suppose.
I have no idea. This is so over my head...
Andi..
Bill
Andi Vajda <va...@apache.org> wrote:
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 problem:
error: Unable to find vcvarsall.bat
And there's no way (I can see) to tell jcc about that compiler, is there?
Have you tried --compiler ?
Andi..
