[news.eclipse.platform.swt] Re: Recompiling SWT

[Jan Schulz <muelleimer@xxxxxxxxxxxxxxxxx>]

* Christophe Cornu <christophe_cornu@xxxxxxxxxx> wrote:
> We have a new gtk makefile which calls gcc instead of driving the linker
> ld 'manually'. This should incidentally fix your problem.

I will have a try. Just by looking at it, how do I have to call it
to set JAVA_JNI?

IVE_HOME   = /bluebird/teamswt/swt-builddir/ive
#IVE_HOME   = /opt/IBMvame1.4/ive
JAVA_JNI=$(IVE_HOME)/bin/include
[...]
CFLAGS = -shared -O -DSWT_VERSION=$(SWT_VERSION) \
-DLINUX -DGTK \
-fpic -fPIC \
-I$(JAVA_JNI)

It's completly useless I think on any but your build PC. What
options do I need to use JAVA_HOME and JAVA_HOME/include as JAVA_JNI
place?

> libswt-gnome.so is used for the org.eclipse.swt.program.Program api, when
> running Eclipse on a gnome desktop (e.g. to find which app is binding to a
> particular extension). It is not strictly required to run SWT apps.

thanks for the information.

Next question is now how to rebuild it on linux/PPC (or just any
arch, which has a JVM and gtk libs). There are several places, where
platform specific code is used. The problem is, that eclipse uses
the fragments and therein the OS and ARCH specific folders. Is it
harmfull to just go on with using -arch x86 an any other linux 
platform, or will I have to patch my way through eclipse (which I
am not able to do... :/ )?

Is that actually the right place to ask this? I don't know who is
responsible for the native parts, especially the launcher...

Thank's for the fast reply!

Jan