On Feb 1, 2010, at 12:52 PM, Daniel Roßberg wrote: > I'm afraid this discussion is losing the common interest. I.e. we > could continue it by private mail or IRC (if I'm logged in ;-}.
What a horrible suggestion to take the discussion private! :-) Developer discussions should be public. Even the lurkers read. Shared knowledge is common knowledge. > I had a different impression: "Unfortunately, this convention [i.e. > release numbers encoded in the library names] conflicts directly with > libtool's idea of library interface versions, ..." (from the libtool > manual) Then they write something about libtool's -release flag. > > However, from the manual I have an idea how it could work: The version > information is part of the .la-file in liked this way into the > executable (which uses this information e.g. for its library search > method during loading). Right? Sort of. Libtool uses the version compatibility information differently for different platforms. For Mac OS X, for example, dylibs actually have an encoded concept of their current version and compatibility versions. So a binary can search at the point of invocation for compatible libraries that meet its requirements. If I recall correctly, GNU BFD libraries have a very similar concept that the GNU linker can take advantage of. The information is definitely included in the libtool archive (the .la file), but that's only useful at link time and for libtool projects. Interesting food for thought, but it would be more beneficial to find a platform-agnostic solution, or at least a solution that is nearly identical across platforms. Cheers! Sean ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
