harperb@frith.msu.edu (Brett Harper) (08/22/90)
I have just completed an Object Oriented toolkit for creating X applications. It all works pretty good and is easy to use, but the size of the executables that it generates! Let me tell you. They 'is huge! A simple program that is 97 lines long that loads a bitmap and displays it compiles to ~900k Could somebody tell me if other object oriented X toolkits produce code that is so obese? Is there anything to do about it. Since the code will be run on a sun4 with at least os 4.0.3 using shared libraries will this be as big of a problem? i.e. will two applications use the same library space? Or will both executable images be loaded in their entirety? How about InterViews, what is a typical executable size for it? Thanks, Brett Harper Case Center for CAEM Michigan State University harperb@frith.egr.msu.edu
schwartz@groucho.cs.psu.edu (Scott Schwartz) (08/24/90)
In article <1990Aug22.164024.12536@msuinfo.cl.msu.edu>, harperb@frith.msu.edu (Brett Harper) writes: | How about InterViews, what is a typical executable size for it? On a Sun4 under 4.0.3, with g++ and the obligatory static linking a few sample interviews applications come out to: text data bss dec hex 278528 40960 5980 325468 4f75c alert 270336 40960 7172 318468 4dc04 dclock 425984 90112 3324 519420 7ecfc graphics 393216 73728 14204 481148 7577c iclass 663552 204800 32044 900396 dbd2c idraw 344064 57344 0 401408 62000 ifb 360448 57344 12588 430380 6912c ifc 253952 32768 3524 290244 46dc4 logo 270336 40960 1620 312916 4c654 mailbox 360448 81920 1292 443660 6c50c squares 327680 57344 788 385812 5e314 sted 270336 49152 4916 324404 4f334 iplot