[mapguide-internals] fdo, linux, rpm and sonames
Walt Welton-Lair
walt.welton-lair at autodesk.com
Fri May 11 10:10:01 EDT 2007
It seems this is just for FDO? MapGuide itself is consistent in its use
of -version-info.
Speaking of -version-info, do we need to update the version-info for any
of our libraries for our upcoming release? See
http://www.gnu.org/software/libtool/manual.html#Versioning for
guidelines on when to change this.
Walt
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Friday, May 11, 2007 3:49 PM
To: mapguide-internals at lists.osgeo.org
Subject: RE: [mapguide-internals] fdo, linux, rpm and sonames
This suggestion makes a lot of sense to me. Practically all Linux
libraries I've dealt with have had the .so.X.X.X naming.
Traian
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Helio
Chissini de Castro
Sent: Thursday, May 10, 2007 10:25 PM
To: mapguide-internals at lists.osgeo.org
Subject: [mapguide-internals] fdo, linux, rpm and sonames
Hi again
During packaging Fdo, i noted that all libraries are generated like:
libFDO-3.2.2.so
libFDO.la
libFDO.so
This is due
libFDO_la_LDFLAGS = -shared \
-release $(VERSION) \
in Makefile.am
The problem with this format is we're unable to use libFDO-3.2.2 for
preload,
instead we're forced to run against libFDO.so. This leads to rpm package
requires all base devel packages in install, like gdal-devel, as we
can't
properly separate runtime libraries from devel libraries.
As an example, mapguide ldload libFDO.so. This is on purpose ?
A simple change from -release to some like this:
-no-undefined -version-info 3:2:2
Can provide this layout:
libFDO.so.3
libFDO.so.3.2.2
libFDO.la
libFDO.so
with will be suitable for packaging and linking, making programs not
rely
on .so devel linrary and reduce the amount of useless devel packages.
Is there any chance to change this in future ? ( remember, this affects
just
*nix builds )
Thanks in advance and sorry by the rant.
--
Helio Chissini de Castro
KDE Developer
Brasil/South America Primary Contact
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
More information about the mapguide-internals
mailing list