[Xastir] Geotiff

[Curt, WE7U]

On Tue, 18 Jan 2005, N1OFZ wrote:

> I built libgeotiff form the
> latest source using ./configure --prefix=/sw and after the make and
> install all I got was the static library.  There is an OS X precompiled
> (but older) version on the geotiff site but it also just contains the
> static library.  Is there a reason why static libraries are bad?

No, not really.  The downside is that you link the library and the
Xastir code together into one executable that sits on your hard
drive, so it's bigger.  If you have multiple programs using the same
library, each one ends up with a copy of the library in it's
executable.  The upside is that you don't have to resolve the
dynamic links when starting up the executable.

For shared libraries, you must resolve those links before the
program will run, and load the library or part of it into memory
along with the executable (skipping demand-loading discussions
here).  The upside to these is that you don't have lots of copies of
the library code sitting around on your hard drive with every
executable that needs them.

So really either type can be used, and many libraries will install
with both a static and a shared version so that either may be used.

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"