[pylucene-dev] Re: can't --compile on Linux (gcj issues again)

[Andi Vajda]

On Wed, 5 Mar 2008, Bill Janssen wrote:

>> I believe that this is another one of these missing class stubs, but
>> haven't figured out which one yet.
>
> I don't think it's a missing class stub, it's a process ordering
> problem.
>
> There's a chicken-and-egg problem here; the --compile command to JCC
> attempts to compile the jcc source files before generating the stubs,
> and there are no stubs for the classes it's trying to include, so it
> always picks up the gcj header files.  I seem to have to first run jcc
> with --build, then with --compile, to get things to work.

Yes, that can be confusing. --compile actually means 'recompile' and assumes 
--build was done at least once before. In fact, --compile is equivalent to 
--install if --build is not specified. That's a debugging feature that helps 
me recompile only the files that changed in jcc when debugging something, 
without regenerating the big __wrap__.cpp file(s) and watching them be 
recompiled. It seems to me that the --compile flag is redundant unless it 
gets changed to compile but not install.

Andi..

>
> Bill
> _______________________________________________
> pylucene-dev mailing list
> pylucene-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
>