Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!ZERKALO.HARVARD.EDU!thakur
From: thakur@ZERKALO.HARVARD.EDU ("Manavendra K. Thakur")
Newsgroups: comp.windows.x
Subject: Ack!  Debugged libX11 is over 9 MB long!
Message-ID: <9012190459.AA05744@zerkalo.harvard.edu>
Date: 19 Dec 90 04:59:26 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 35


I decided to compile debugged versions of the X libraries, and much to
my suprise, libX11_d.a came out to be over 9 MB (that's megabytes)
long!

Here are the actual numbers for comparison:

-rw-r--r--  1 root       268982 Dec 18 20:07 libX11.a
-rw-r--r--  1 root      9345410 Dec 18 20:08 libX11_d.a

-rw-r--r--  1 root       312878 Dec 18 20:08 libXt.a
-rw-r--r--  1 root      2972230 Dec 18 20:08 libXt_d.a

Note how libXt.a is larger   than libX11.a   by 44 kilobytes.
Note how libXt_d.a *smaller* than libX11_d.a by 6.4 megabytes.

Most likely, this is because Xlib is composed of five times as many
object files than the Xt library (249 vs. 46).  This must be why the
debugged libraries are not compiled by default!

So I'm wondering: is there any chance that the X Consortium folks
would consider collapsing Xlib source files into a smaller number of
larger sized files?  That way, at least the debugged version of the
library won't be so ridiculously large.

But given that Xlib is such a behemoth already, is my wish for fewer
source files a pipe dream?

Oh yeah, I compiled these libraries with cc on a Sun 4 running SunOS
4.1.1.

Manavendra K. Thakur			Internet: thakur@zerkalo.harvard.edu
System Manager,	High Energy Division	BITNET:	  thakur@cfa.BITNET
Harvard-Smithsonian Center for		DECNET:	  CFA::thakur
Astrophysics				UUCP:	  ...!uunet!mit-eddie!thakur