Unresolved symbol errors

From: John Peter Gormley <jgormley_at_scu.edu.au>
Date: Wed, 16 May 2001 09:55:55 +1000

Sent on behalf of Sheryl Bruggy, please respond to Sheryl at
sbruggy_at_scu.edu.au

In the last few months I have had to compile several very complex
applications which included multi-level library builds. That is,
libraries which included other libraries which included other libraries
etc. Each time I ended up with unresolved symbol errors.

Does anyone have a simple set of rules for building these types of
applications? For instance, if you begin with a static library, do all
libraries included in the build have to be static or can some be shared
and vice-versa?

I had previously believed that shared libaries were a better
option as they resulted in a smaller footprint and any application
compiled with these libraries did not have to be re-compiled if the
libraries were updated. However, now I am not so sure.


Regards
Sheryl Bruggy
Systems/Network Administrator - Unix
sbruggy_at_scu.edu.au
Received on Tue May 15 2001 - 23:54:27 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT