On 2014-02-03 22:28+0100 Nils Gladitz wrote:
Archives (static libraries) are basically collections of object files.
They are themselves not yet linked to libraries nor do they record
dependencies[...]
Yeah, that confirms the fundamental mental model I was using
concerning static libraries.
Obviously for case 2 (static C++ library dynamically linked to
libstdc++) the static library (archive) will not contain code from
libstdc++. But what happens for case 3 when the static C++ library is
statically linked to libstdc++? Does the static library in this case
contain all the needed code from libstdc++? If so, this make an
important distinction between case 2 and case 3, but otherwise they
would be the same.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
