home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.misc
- Path: sparky!uunet!ocsmd!finnbogi!obi
- From: obi@finnbogi.ocs.com (Obi Thomas)
- Subject: Shareable libraries problem (Not again!).
- Message-ID: <By081J.2L1@finnbogi.ocs.com>
- Sender: obi@finnbogi (Obi Thomas)
- Reply-To: obi@finnbogi.ocs.com
- Organization: Online Computer Systems, Inc.
- Date: Fri, 20 Nov 1992 07:41:42 GMT
- Lines: 26
-
- Ok, for the (n + 1)th time, could someone please explain yet again how to
- break a shareable library into .so and .sa parts? I know the standard
- explanation, "Put initialized data in the .so part and the .sa part." But
- what I see of the MIT X11R5 source code doesn't jibe with this.
-
- For example, in mit/lib/Xt, there are dozens of initialized structures and
- arrays (the class structures and the resource arrays). But if I understand
- the Imakefile right, these all go in only the .sa part. Why? Isn't this in
- conflict with the commonly stated rule above?
-
- What about C++? The virtual function tables for a class are initialized
- data, right? What do I do with them? What about static objects which have
- constructors? I'm trying to make shareable libraries out of some of our
- C++ class libraries and not having much luck --- I keep getting unresolved
- externals. Some of these go away when I (pretty much at random) stick
- different things in the .so and .sa files, but it's hopeless because I'm
- flying blind here. I know it's possible because the C++ runtime library is
- shareable --- I just don't know what to do.
-
- All this has me writhing in pain, so any tips would be greatly welcome.
- Also appreciated would be the names of books/papers that discuss this (all
- I have is the Sun Programmers Overview and the paper on shareable
- libraries on the Sun demo CDROM).
-
- I'd prefer answers by email and I'll post a summary if there's interest.
- Thank you.
-