[fdo-internals] RE: Common Xerces for MapGuide and Fdo

[Greg Boone]

I am not opposed if we can maintain a option to allow users to build against an installed SDK version or a locally 'built-from-source' version. For clients that require the need to maintain strict binary compatibility, the Apache code can be maintained in a local developer-specified location and used from there, depending on environment setup.

Greg.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Thursday, July 01, 2010 10:18 AM
To: FDO Internals Mail List
Subject: [fdo-internals] Common Xerces for MapGuide and Fdo

Hi list,

As part of the MapGuide Oem library upgrades for the next release, we will be moving to Xerces 3.1.0 (or maybe 3.1.1) to match Fdo.  The work is being done by Rohit, our Google Summer of Code Student.  For MapGuide, we are intending to remove Xerces from our source tree and use previously installed "-dev" packages on Linux and official Xerces "SDKs" on Windows.  Since Xerces 3.1.0 is not available on CentOS 5, we will be building and distributing the RPMs ourselves.

In an effort to share the same physical library on both Linux and Windows, we were wondering if it would make sense to follow the same process for Fdo, ie. pull Xerces out of the tree and build against an "installed" version of Xerces for both Linux and Windows?  As a side note, building against installed "/usr" libs on Linux would bring us one step closer to Debian / Ubuntu packaging compliance.

Is this approach reasonable?

Regards,
Trevor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20100707/fad7d04a/attachment.html