Xref: utzoo comp.windows.x:15095 comp.windows.misc:1261
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!cs.utexas.edu!wuarchive!decwrl!chico.pa.dec.com!klee
From: klee@chico.pa.dec.com (Ken Lee)
Newsgroups: comp.windows.x,comp.windows.misc
Subject: Re: xclock, xcal, xbounce
Message-ID: <2098@bacchus.dec.com>
Date: 14 Nov 89 19:41:16 GMT
References: <24003@cup.portal.com> <8910172113.AA02246@chief.xpiinc.uu.net>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Organization: DEC Western Software Laboratory
Lines: 22

In article <24003@cup.portal.com>, swatt@cup.portal.com (Steven Edward
Watt) writes:
> More bad news:  dxclock was written with UIL, and hence takes up almost
> 1.3MB!!!!   (Almost 2MB on a DECStation 3100!)  No problem, right?  Mutter
> about virtual memory and paging and neat things like that...
>
>   Anybody know of a nice way to do shared libraries?

One way to fake shared libraries is to take advantage of UNIX's (and
Ultrix's) shared text capability.  Try linking a bunch of your UIL
programs together and they'll share the text of the Xt, Xlib, and UIL
libraries.  DECwindows dxclock, for example, is linked with dxcalendar
and some others.  The real memory use is much smaller than the 1.3MB
you mention.  Other commonly used DECwindows programs, such as
dxsession, dxterm, and dxwm, are also linked together.  The links are
both disk hard links (try "ls -i" on /usr/bin) and ld compile-time
links.  This isn't a cure all, but may save you some disk and memory.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@decwrl.dec.com
uucp: uunet!decwrl!klee