Hi Takashi,
Takashi Okamoto wrote:
> However, one is disappointed. Sablepath isn't compatible with
> classpath. For examples, you modified following:
>
> System.loadLibrary("java-io");
>
> ORP 1.0.6 works with sableepath but it shows warning message because
> JNI library name is different.
>
> If you chage JNI library name to classpath style like "javaio", orp
> may work fine with Salbepath though sablepath is for Sable VM...
In fact, Sablepath 0,1,7 does NOT work yet with SableVM (or I should say
SableVM does not work yet with this Sablepath version;-).
The reason for the name change is that I wanted a "canonical" naming
scheme for native libraries (to avoid names like "cpgdkpixbuf"), so I
thought naming the libraries according to their java package name by
replacing "." with "-" would make those names intuitive to guess/derive.
Originally I tried replacing "." with "_", but I discovered that using
"_" in a library name is a bad idea for libtool libraries...
Also, you can notice that I regrouped "javamath" and "javalang" into a
single library "java-lang". I see not good reason to create more than
one native library per package.
I have not looked carefully at ORP, but the changes to ORP should
normally be quite minimal to get it to work with sablepath.
Let me know of any problem you discover.
Oh! By the way, if you have any idea how to get the AWT classes to
compile without having gcc complain about dereferencing incomplete
types, let me know... [This code is in Sablepath's CVS tree only.]
Have fun!
Etienne
--
Etienne M. Gagnon http://www.info.uqam.ca/~egagnon/
SableVM: http://www.sablevm.org/
SableCC: http://www.sablecc.org/
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
