Nathan Meyers writes:
> On 22 Oct, Greg Wolodkin wrote:
> > 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..)
>
> Hmmm... never seen that complaint before.
>
> The JDK1.2 scheme allows a non-AWT application to run without any
> dependencies on finding a Motif library, and without shipping a bunch
> of different JVMs the way Blackdown JDK1.1 does. It's good news for
> deployment on servers.
>
> I'm not clear to me what is now made impossible. Could you clarify?
Impossible may be stretching it. But suppose you have a program
which already does a lot of Motif stuff, and you want to add some
Java capabilities. You need to link your main program against
libXm.a or libXm.so, and now libawt.so is going to suck in another
copy of Motif.
At a minimum, you've got a 2MB bigger footprint than you need. In the
worst cast, there is static data in Motif that I now have two copies
of, and I suspect that is going to cause lots of trouble. I haven't
dug into it yet, but a simple frame test created in Java via JNI (it
works in 1.1.7 no problem) now works OK in 1.2 until I link the main
program against Motif, at which point the java thread seg-faults.
Would it be possible to distribute another libawt.so which doesn't
have Motif built in? (Sort of like java and java_dyn used to be?)
If I have to build my own JDK, I'm much more restricted in how other
people can use it. But having all of the Motif symbols live in awt
and not be exported for my main program to use is a bummer. It
literally prevents me from using Motif and Java together on Linux,
at least from what I can see.
Thanks for any advice or thoughts -
Greg
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
