On Wed, Sep 14, 2005 at 09:52:00AM -0600, Shaun Jackman wrote: > 2005/9/14, Michael Koch <[EMAIL PROTECTED]>: > > UURGH, NO. This will break SWT on 32 bit archs - if it works on 64 bit > > archs at all. > > > > You cannont compare normal C code with JNI C code. JNI C code has much > > higher restrictions. > > There's that cry of outrage! Hehe. Are there any 32-bit architectures > where int is not synonymous with long? The patch I plan on applying > follows. Incidentally, this worked just fine on i386, tested with > swingwtdemo as a native gcj application, and with Azureus using the > Sun JVM.
You replace jint (which is garanteed to be 32 bit) with long which dont has this garantee. Why dont you just build the native sources that upstream supplies for 64 bit systems? That is what I do in the eclipse build works very fine. BTW: My Eclipse packages are ready to replace your SWT. When you give me your okay I can imidiately upload it to the archive (via some sponsor). I think this would be the easiest solution at all. Cheers, Michael -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
