Andi Vajda <va...@apache.org> 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 do you think? > > Remember how ? from what ? You want jcc to invoke the compiler, tell it > which one via --compiler.
JCC always has to invoke *some* compiler, to compile the stubs that it generates. Right? The question is, must it always use the same compiler that JCC itself was compiled with? And I think the answer is, no. You can compile JCC with VS and you get a standard Python extension, albeit needing to link against some compatible JVM DLL. You can then take that extension and move it to a machine without VS, but having MinGW, and use it to generate and compile stubs for some Java jar file, using MinGW as the compiler. I think. > > 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. As I outline above. > I have no idea. This is so over my head... I always feel like I'm banging my head against the wall, getting things done on Windows the hard way, but people are clamoring for a Windows installer for UpLib, so... Bill
