Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!ctrsol!ginosko!aplcen!jhunix!ins_ajsk
From: ins_ajsk@jhunix.HCF.JHU.EDU (Jon Kay)
Newsgroups: comp.windows.x
Subject: SunOS4 Xlib shared library
Keywords: works
Message-ID: <2465@jhunix.HCF.JHU.EDU>
Date: 7 Sep 89 17:23:55 GMT
Organization: Johns Hopkins
Lines: 31

Those of you with Suns running SunOS 4.whatever might be interested in
the following:


I recently created an SunOS shared library out of Xlib, and it seems
to work really nicely.   I have a 4-meg Sun 3/60, so memory is a
really sore point with me.  Clearly paging is way down now.
Each executable I've compiled grew smaller by 60-100K after compiling
with the Xlib shared library, plus the commonly used Xlib code pretty
much stays in memory.

I went about it in a very simple-minded way: I simply used
make CC="cc -pic -O2"
rm libX11.a
ld *.o -o libX11.so.11.3
in the lib/X directory and installed libX11.so.11.3 in /usr/lib.
I did NOT perform the separation of modified and never-modified
initialized data recommended in the manuals; that would have taken a
long time and there isn't much data in the Xlib in any case.  I also
"sharified" libXt.a and libXaw.a, but those seem to be losing choices;
nothing I've compiled so far uses them except for xterm.  Mileage on
those may vary, though.... 

If anybody decides to do it "right" or comes up with some other
improvement, please let me know....


					Jon Kay

"What am I doing?"
		-A JHU Math professor who shall remain nameless.