I think this is so that people who use AWT components in a JNI
started Java program do not need to have Motif installed on
the box. With Motif statically linked into libawt.so, this
is not a problem (it was a problem with 1.1.7).
I hope that helps
Mo DeJong
> p.s. what's the motivation behind pushing the Motif dependencies
> into libawt.so in the 1.2 builds? This seems to make it
> impossible to have a Motif application which uses the JNI
> to do Java stuff (with AWT, anyway). Probably I'm missing
> something, but I thought the scheme with 1.1.7 was pretty
> happening (at least for JNI..)
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]