Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ucsd!sdcc6!odin!bruss
From: bruss@odin.ucsd.edu (Brian Russ)
Newsgroups: comp.windows.interviews
Subject: Shared libraries / InterViews
Message-ID: <18377@sdcc6.ucsd.edu>
Date: 17 Apr 91 02:37:43 GMT
Sender: news@sdcc6.ucsd.edu
Organization: CSE Dept., UC San Diego
Lines: 37


	(This may not be quite the right place for this, as the question
concerns shared libraries more than InterViews, but ...)

	We are developing several applications with InterViews 2.6.  As
the compile times and executable sizes increased, we started to wonder
whether shared object files would solve some of our problems.  Several
of the executables are several meg in size, and it seems like a lot
of that size is either libInterViewsX11.a itself, or our collections
of graphics classes built on top of InterViews.  Also, several of these
applications would be running concurrently, so a 8 or 16 meg Sun
(Sparcstation) starts spending a lot of time swapping.

	So, the questions are:

	(1)  Would shared libraries help at all?

	(2)  Can libInterViewsX11.a be converted into a shared library?
	     How?

	(3)  Can our user libraries (just collections of C++ classes
	     derived from InterViews) be converted into shared libraries?
	     How?

	(4)  Are there any guidelines about what can and can't be shareable?
	     I think the general idea is that code that uses global or
	     static data is out, but I may be over-simplying this, or maybe
	     I'm just plain wrong.

	Thanks for any help ...

					Brian

-- 
Brian Russ
CSE Department, UC San Diego
..!sdcsvax!bruss	bruss@beowulf.ucsd.edu