[fdo-internals] Making the cmake build usable with MapGuide

[Traian Stanev]

Rename one of the classes or use a namespace -- otherwise the symbol resolving will use the first class it finds with that name. We've had the same issue before with classes being duplicated between SDF and MapGuide and then one of them slightly changes, which then causes crashes due to binary incompatibility (that's when I had to add the RS prefix to some of the classes on the MapGuide side so that they don't conflict).

Traian


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Sunday, June 16, 2013 10:46 AM
To: fdo-internals at lists.osgeo.org
Subject: Re: [fdo-internals] Making the cmake build usable with MapGuide

Hi Jack,

-Bsymbolic made no difference at all

One thing I noticed is that the cmake build is putting a whole lot more weak symbols into its object files than the automake one. An objdump or nm shows the cmake-produced object files have way more symbols than the automake-produced object files. 

Is this a potential problem? Are there g++/ld flags to control this?

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Making-the-cmake-build-usable-with-MapGuide-tp5060074p5060408.html
Sent from the FDO Internals mailing list archive at Nabble.com.
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals