[Kde-bindings] Undefined Reference to 'typeinfo for ....
Richard Dale
Richard_Dale at tipitina.demon.co.uk
Wed May 19 10:05:06 UTC 2004
On Wednesday 19 May 2004 10:34, Fabien Renaud wrote:
> Ok, I now have all the .java
> What is the easiest way to compile them all ?
> javac searches in org.kde.qt ( and of course doesn´t find ).
> Have I to put all .java in this directory first ?
There will be more java classes output by kalyptus than you need for the
project. So I'd copy them in something like this:
$ cd qtjava/javalib/org/kde/qt
$ for FILE in *.java ; do
$ cp <kalyptus generated code dir>/$FILE .
$ done
Investigate which files were missing, and check if ok. Missing files should
either be part of the qtjava runtime such as qtjava.java and Invocation.java,
or not needed anymore (I think there used to be interfaces called
*EventHandler.java which aren't generated anymore). You can include the
interfaces called <class name>Signals.java, which are for documentary
purposes, but they tell you which signals a class emits in java terms.
Generate the .h headers with javah like this:
$ for FILE in *.class ; do
$ NAME=`echo $FILE | sed 's/.class//'`;
$ echo $NAME; javah -classpath
'../../..:../../../../../qtjava/javalib/qtjava.jar' org.kde.koala.$NAME ;
$ done
$ for FILE in org_kde* ; do
$ NAME=`echo $FILE | sed -e 's/org_kde_koala_//'`;
$ echo $NAME;
$ mv $FILE $NAME;
$ done
Copy the .h files to the qtjava/javalib/qtjava directory and build the .cpp
sources there.
I'll get a copy of Qt/E so I can try it out myself and should be able to help
- it will be interesting if it works.
-- Richard
More information about the Kde-bindings
mailing list