Re: Native Compile to Shared Library?

["Michael Purdy" <mpurdy at BTBOCES dot ORG>]

The thought was to be able to write plug-ins for an internal application and allow the plug-ins to be natively compiled, but still be able to be called from the main application.  The main application's gui is written in swing and therefore is not a good match for gcj native compiling.  However, if the plug-ins could still be native gcj compiled and interface efficiently with the main application (running in the sun jvm due to Swing), we would be able to preserve the main application.  

In my hopeful plan (which seems unattainable), I would have had the plugs still developed in Java and native compiled with gcj.  Turns out I'll probably just have them remain 'regular' bytecode java so the sun jvm/main app handles them correctly or have them call platform specific native c++ where performance boosting is needed.

Thanks for the info.

Mike

>>> Andrew Haley <aph@redhat.com> 11/03/05 10:51 AM >>>

 > The goal would be to allow the necessary set of classes to be
 > native compiled, but still written in Java.  Thus, we would not
 > need to have 3 codebases for the native code in c++ on each
 > platform.

I don't quite know why you want to do this.

Andrew.