Problem compiling provider for Autodesk Map 2010

8 messages Options
Embed this post
Permalink
Bruno Scott

Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
I've succesfully compile FDO using
  https://svn.osgeo.org/fdo/branches/3.4
and
  https://svn.osgeo.org/fdo/trunk

When i try to load one of these PostGIS provider, Map 2010 can't load the dll
I have the same error if i use my own compilation of the sdf provider.

It must be a version mismatch.
I tought that all 3.4.* dll would be binary compatible, is that true?
or maybe i'm not compiling them right!
Witch version i should use for AutoCAD Map 2010?


Bruno Scott
Romica Dascalescu

RE: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
Hi Bruno,

There was a change of parameter type in function Create Exception (we changed some parameters from wchar_t* to const wchar_t*) and this breaked FDO 3.5 (trunk) with Map2010 compatibility (Map is looking for a different function signature).

Romica.
________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Bruno Scott [[hidden email]]
Sent: Friday, April 17, 2009 9:54 AM
To: [hidden email]
Subject: [fdo-internals] Problem compiling provider for Autodesk Map 2010

I've succesfully compile FDO using
  https://svn.osgeo.org/fdo/branches/3.4
and
  https://svn.osgeo.org/fdo/trunk

When i try to load one of these PostGIS provider, Map 2010 can't load the dll
I have the same error if i use my own compilation of the sdf provider.

It must be a version mismatch.
I tought that all 3.4.* dll would be binary compatible, is that true?
or maybe i'm not compiling them right!
Witch version i should use for AutoCAD Map 2010?


Bruno Scott
--
View this message in context: http://n2.nabble.com/Problem-compiling-provider-for-Autodesk-Map-2010-tp2650844p2650844.html
Sent from the FDO Internals mailing list archive at Nabble.com.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Bruno Scott

RE: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
I understand it could be broken in the trunk(3.5)
but why would the branche/3.4 have the same errors?

Bruno
Greg Boone

RE: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
FDO 3.4 should be fine. We recently added a DELAYLOAD setting to FDO. Make sure the FDO bin directory is in the path.

Greg

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruno Scott
Sent: Friday, April 17, 2009 10:05 AM
To: [hidden email]
Subject: RE: [fdo-internals] Problem compiling provider for Autodesk Map 2010


I understand it could be broken in the trunk(3.5)
but why would the branche/3.4 have the same errors?

Bruno
--
View this message in context: http://n2.nabble.com/Problem-compiling-provider-for-Autodesk-Map-2010-tp2650844p2650897.html
Sent from the FDO Internals mailing list archive at Nabble.com.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Bruno Scott

Re: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
In reply to this post by Bruno Scott
I have added "C:\Program Files\AutoCAD Map 3D 2010\FDO\bin" to the path
and i still have the same problem.
Map says
    Unable to create connection to provider 'OSGeo.PostGIS.3.4'
    Unable to load the FDO Provider: The specified procedure could not be found
Bruno Scott

Re: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
In reply to this post by Bruno Scott
oops, i got you wrong
not adding the fdo in the path for running Map 2010
but for compiling...
I will double check and recompile...
Greg Boone

RE: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
If adding the path works, then we may have to revisit the DELAYLOAD implementation in FDO. FDO was designed so that its path need not be included in the system path. This was done so that side by side execution of applications using FDO can occur.

Greg

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Bruno Scott
Sent: Friday, April 17, 2009 10:40 AM
To: [hidden email]
Subject: Re: [fdo-internals] Problem compiling provider for Autodesk Map 2010


oops, i got you wrong
not adding the fdo in the path for running Map 2010
but for compiling...
I will double check and recompile...
--
View this message in context: http://n2.nabble.com/Problem-compiling-provider-for-Autodesk-Map-2010-tp2650844p2651085.html
Sent from the FDO Internals mailing list archive at Nabble.com.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Bruno Scott

RE: Problem compiling provider for Autodesk Map 2010

Reply Threaded More More options
Print post
Permalink
Ok i'm up and running.
Some of my env variable were still pointing to the trunk when i was compiling the branche 3.4 :(
Thanks Greg.

By the way i have removed all fdo path in my path and it works fine.
So i guess you won't need to revisit your delay load stuff :)

Bruno


Greg Boone wrote:
If adding the path works, then we may have to revisit the DELAYLOAD implementation in FDO. FDO was designed so that its path need not be included in the system path. This was done so that side by side execution of applications using FDO can occur.

Greg