[fdo-users] Help with compiling and deploying providers on windows

[Greg Boone]

Jason is correct. Binary compatibility has changed. The FDO trunk (FDO
3.3.0) is no longer compatible with MG OS 1.1.0. MG OS is built on FDO
3.2.0.

For MG OS 1.1.0, your best bet is to download the FDO 3.2.0 source code
from:

http://fdo.osgeo.org/downloads.html

Specifically, take the following tar files...

fdo-3.2.0.tar.gz
fdordbms-3.2.0.tar.gz

Jason is also correct that MG OS 1.2 will be building against FDO 3.2.2
which can be found under the following svn locations:

FDO: https://svn.osgeo.org/fdocore/branches/3.2.x
MySQL:
https://svn.osgeo.org/fdordbms/branches/3.2.x/Providers/GenericRdbms

Greg

-----Original Message-----
From: fdo-users-bounces at lists.osgeo.org
[mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Friday, March 16, 2007 7:50 PM
To: fdo-users at lists.osgeo.org
Subject: RE: [fdo-users] Help with compiling and deploying providers on
windows

'The feature source is invalid. Reason: An exception occurred in FDO
component. Unable to load the FDO provider: The specified procedure
could not be found.'

I believe that this is because the current trunk of FDO is not
compatible with MapGuide Open Source.  The current released version of
MapGuide Open Source only works with FDO 3.2.0 (and maybe some slightly
later builds, but binary compatibility was broken at some point).

The next version of MapGuide Open Source (betas starting in early April)
will be using FDO 3.2.2.  This is still not FDO trunk, which I believe
is the foundation for 3.3.x 

That said, I can't find the tag for 3.2.2, so maybe I have everything
wrong. :)

Jason
_______________________________________________
fdo-users mailing list
fdo-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-users