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
My current app is built across 4 platforms (win32, os x, linux 32 bit and linux
64 bit), only two of which I have administrative control over. Recently, I
upgraded to soci 3.x and now I have to keep separate makefiles for the two
systems until I get around to recompiling soci for the linux sides and coax the
admin to replace them for me. I would do the linking myself, but, my code is
open source, and the makefiles wouldn't work on other folk's systems.
Just curious if there is a reason that it's done this way. If not, is there a
place I can request that it be done in future builds?
_________________________________________________________________
Bing™ brings you maps, menus, and reviews organized in one place. Try it now.
http://www.bing.com/search?q=restaurants&form=MLOGEN&publ=WLHMTAG&crea=TEXT_MLOGEN_Core_tagline_local_1x1------------------------------------------------------------------------------
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
