It is possible to write programs that know nothing about the binary
executive. I could write my own program that does my own memory
management but uses the algorithms with libDX or others. Since this
is a full toolkit of algorithms as well as the binary--most of us
always include full libraries as well. Another reason to include them
is if a user decides to build inboard or outboard modules. These
types of modules do not link into the runtime, but actually use the
libraries.
David
Moi!
I'm currently preparing OpenDX 4.3.0 packages for Debian's Linux
distribution. Peeking through other binary distributions, past and
present, I note than every one includes the various static libDX* libs
in $DXROOT/lib_linux. But isn't it sufficient to just ship arch.mak as
well as all the header files? If I understand correctly, even external
modules are never linked against any of those libs, but the symbols are
resolved from the main binary when the module is loaded instead. So is
there a case where one would want to see libDX* distributed that I'm
currently not thinking of? Otherwise we might easily reduce the size of
OpenDX binary packages by almost a factor of two.
Regards,
Daniel.
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
