public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: got JNI; but only just :-)
Date: Sat, 12 Apr 2008 20:53:00 -0000	[thread overview]
Message-ID: <47FFD8E7.5060803@redhat.com> (raw)

FYI,

I've just pushed changes to frysk's build system that add the ability to 
build JNI code vis:

- automatically generate required jni headers
- compile */jni/*.cxx files into a separate shared object

while at the same time continuing to build the existing CNI code.  By 
being able to build/run both side-by-side we'll hopefully help to ease 
the migration pain.

In the frysk-sys directory, I've also added stub C++ JNI functions (they 
just throw an exception) for all the required native methods.  You can 
invoke TestRunner, but using JNI and these stub-functions, with the 
script JniRunner vis:

$ ./JniRunner
Exception in thread "main" java.lang.RuntimeException: 
../../frysk/frysk-sys/frysk/config/jni/Config.cxx:Java_frysk_config_Config_createBuildConfig 
not implemented
        at frysk.config.Config.createBuildConfig(Native Method)
        at JniRunner.main(JniRunner.java:57)

(Did I mention that all the JNI functions were stubs and just threw 
exceptions? :-)

Next I'm going to work my way through frysk.config, frysk.rsl, and 
frysk.sys.

The lib/* libraries are an opportunity waiting to happen :-)

Andrew

             reply	other threads:[~2008-04-11 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 20:53 Andrew Cagney [this message]
2008-04-12 21:01 ` Mark Wielaard
2008-04-14 13:26   ` Andrew Cagney

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=47FFD8E7.5060803@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sources.redhat.com \
    /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).