Newsgroups: comp.windows.x.motif
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!ispd-newsserver!sydorow
From: sydorow@bisco.kodak.com (Steve Sydorowicz)
Subject: Re: Motif 1.1.2 and SunOS shlib
Message-ID: <1991Jun4.115138.29103@ssd.kodak.com>
Sender: news@ssd.kodak.com
Organization: Eastman Kodak
References: <9106021754.AA25809@mview> <9106031823.AA01972@sirius>
Distribution: inet
Date: Tue, 4 Jun 91 11:51:38 GMT

tsang@ISI.COM (Kam C. Tsang) writes:

>[This is really for Scott Weitzenkamp.  Our mailer can't handle uunet
>address.  Sorry for wasting bandwidth.]
>
>> How hard is it to make SunOS shared libraries for Motif 1.1.2?
>
>Building sharable library for motif is easy.  Just compile the motif
>files with the -pic flag and link the object files (ld -o libXm.so.1.1
>-assert pure-text *.o) .  One complication is that in 1.1 motif has
>grown to size beyond what Sparc can handle, so you need to splt the
>library into two and probably call them libXm1.so.1.1 and
>libXm2.so.1.1, and your applications will have to link with -lXm1
>-lXm2.  You can play with your Imakefile to make it happen, but since
>

To avoid the size problem, you can use "-PIC" in place of "-pic".
Sparc cc defaults the global offset table to 8K (pic). This can be increased
to allow 32 bit addresses via PIC.

Of course, using dbx on applications that link in shared libraries seems
to be somewhat of a crap shoot. Typically, you can not look into the shared
library (same as on SUN3). However, dbx will also dump core on *startup*
sometimes.  (Haven't figured out how to avoid this though...)

Hope this helps...

-- 
--------------------------------------------------------------------------------
Stephen J. Sydorowicz                                 Azatar Computer Systems
REPLY TO: sydorow@bisco.kodak.com                     (716)726-5636
		Opinions expressed do not reflect those of my employer