[prev in list] [next in list] [prev in thread] [next in thread] 

List:       poi-dev
Subject:    Re: GCJ Native Library Success
From:       TJ Mather <tjmather () maxmind ! com>
Date:       2002-11-17 15:04:05
[Download RAW message or body]

Hi,

My next steps are:

1. Submit gcj PRs for the bugs I encountered, checking against the latest
GCJ CVS HEAD.  I'll also check the PRs you cc'ed to me to make sure
I don't submit duplicate bug reports.

2. Clean up the build somewhat.  (low priority)

3. Write an Excel export filter for KSpread.  (high priority)

I have no plans to compile a win32 POI library (i'm running Linux).
Could you Cygwin to compile the win32 POI library?

Thanks,
-TJ

P.s. I'm very happy with the purist workaround, because even though
the gcj team will fix the bugs, it is helpful to have the KOffice
Excel export filter work in GCJ 3.2 as well as later versions.

On Sun, 17 Nov 2002, Martin Aliger wrote:

> Hi,
> 
> Excelent work! I was trying the same but stopped by some bug in gcj
> runtime for now. I tried to compile directly from .java into native
> code. It works now but resulting code does not work yet.
> 
> That patch I made before was meant more as suggestion to recode to mine
> purist style, but gcj seems to have problems with compiled .class files
> containing these ugly interfaces. There is no such problem with .java so
> when gcj team fix that this should not be needed. Since that it is good
> workaround (I still think it is good idea anyway ;-))
> 
> Now I'm going to test your lib and continue to compile directly from
> sources (should result in more efficient code and should be more
> maintainable)
> 
> Finally, do you plan to try compile win32 POI library? I'd like to see
> one...
> 
> Regards,
> Martin Aliger
> 


--
To unsubscribe, e-mail:   <mailto:poi-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:poi-dev-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]