Eric Torstenson wrote: > This might be the wrong place to ask...if so, I apologize in advance. > > Why does soci not follow the convention of symbolically linking > libsoci.so -> lobsoci.3.so -> libsoci.3.3.so
If you are talking about autotools-based build, then I believe it's me. I decided to follow Boost convention regarding naming library files. See "SOCI library names" comment in this script: (http://soci.git.sourceforge.net/git/gitweb.cgi?p=soci/soci;a=blob_plain;f=src/configure.in;hb=HEAD) Personally, I'm a strong antagonist of libtool and I really didn't want to follow its best practices, but get prepared to drop libtool at some point and use CMake (or bjame) as Boost does (no libtool!). I'm slowly drifting away of autotools as they are Unix-oriented. I hope to find time soon to rewrite build configuration to CMake so all popular platforms and toolsets can benefit from single configuration and I will be able to get rid of the hassle of manual maintenance of Visual Studio projects. It means, I may stop maintaining autotools-based configuration soon, unless somebody will take over the task of autotools maintenance. Volunteers are welcome! Best regards -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
