public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: java@gcc.gnu.org, kde-java@kde.org
Subject: qtjava and GCJ update
Date: Tue, 02 Apr 2002 21:08:00 -0000	[thread overview]
Message-ID: <3CAA8BED.8030102@waitaki.otago.ac.nz> (raw)

I have committed a fix for GCJ's java.util.IdentityHashMap that was 
causing JNI crashes with qtjava. The "ScribbleWindow" demo from 
kdebindings-2.2.2 should be running fine with GCJ 3.1 now. I have not 
been able to reproduce Richard Dale's problem which seems like a 
different issue.

Here's what I did to get it running:

1. Install qt-devel, kdelibs-devel, and kdelibs-sound-devel from Redhat 7.2.

2. Download kdebindings source from 
ftp://ftp.kde.org/pub/kde/stable/2.2.2/src/kdebindings-2.2.2.tar.bz2

3. unpack and ./configure --with-qt-dir=/usr/lib/qt-2.3.1

4. cd qtjava; make

5. cd javalib

6. Compile qtjava java source into a shared library:
gcj -classpath . org/kde/qt/*.java -shared --jni -o libqtgcj.so
(the --jni option tells gcj that "native" methods will be implemented 
using JNI, this is important. You can also add -O2 to get a smaller 
faster library, but it will take longer to build)

7. copy the qtjava JNI library into the current directory so it will be 
easier to get at
cp javalib/qtjava/.libs/*.so .

8. compile ScribbleWindow
gcj test/ScribbleWindow.java --main=ScribbleWindow -o scribble -L. -lqtgcj

9. set runtime library path
export LD_LIBRARY_PATH=.

10. run it
./scribble

11. scribble!!

regards

Bryce.


             reply	other threads:[~2002-04-03  5:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 21:08 Bryce McKinlay [this message]
2002-04-02 21:17 ` Bryce McKinlay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CAA8BED.8030102@waitaki.otago.ac.nz \
    --to=bryce@waitaki.otago.ac.nz \
    --cc=java@gcc.gnu.org \
    --cc=kde-java@kde.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).