[fdo-internals] Naming Conventions for debug build???

Traian Stanev traian.stanev at autodesk.com
Wed Apr 8 10:20:11 EDT 2009

This way you can use a debug build of MapGuide against an installed or otherwise available release build of the FDO SDK. If the debug MapGuide linked to Fdod.dll instead of Fdo.dll, you would be forced to compile your own debug FDO in order to compile a debug MapGuide. 


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of UV
Sent: Tuesday, April 07, 2009 9:37 PM
To: fdo-internals at lists.osgeo.org
Subject: [fdo-internals] Naming Conventions for debug build???


in the mapguide project and elsewhere the debug versions of the 
libraries have a d suffix in their names.
In the FDO build this is not the case.
Basically having different library versions with the same name on the 
system seems not like a good way to go.
I noticed this as a factor in introducing additional configuration 
problems into my developing system.

Is there a good reason to do it like this or is this just an unfinished 
piece of configuration management and things have not been aligned 
properly as yet ???

Any thoughts?

fdo-internals mailing list
fdo-internals at lists.osgeo.org

More information about the fdo-internals mailing list