[mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010

Sat Apr 2 03:18:23 EDT 2011

Hi Trevor and Greg,

Thank you very much for the good feedback and discussion. I understand there might be issues to make FDO v90 and mg v100 work together. And there will be tests.

And for PHP and Apache, it is really an issue. We will investigate deeper here.

Thanks,
Mars 

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Saturday, April 02, 2011 5:35 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010

Hi Greg,
As long as someone does the interop testing then fdo v90 and mg v100 should be ok.

For Mapguide Oem, someone should also check v100 compilation of the whole tree. PHP, Apache may be problematic. If I recall, v90 windows binaries for Apache were hard to find.

Sent from my iPhone

On 2011-04-01, at 3:03 PM, "Greg Boone" <greg.boone at autodesk.com> wrote:

> If GDAL Extensions is and only accessed through the FDO GDAL provider and it turn the GDAL binary (gdal1x.dll), then it should not be a concern leaving it on v90 as the FDO Provider, the GDAL DLL and the GDAL extensions will all be on the same runtime. The FDO API will guarantee runtime interoperability at the level of its API. If MapGuide uses it the GDAL extensions directly, then there could be issues if there is memory allocation/de-allocation across that boundary, etc., and we would need to discuss this further. 
> 
> As for your desire to have both FDO and MapGuide on v100, I really do appreciate the concern, and have received similar feedback from other parties. However, I cannot state that is will happen this year. Nor have I heard any real show stopping arguments why MapGuide on v100 cannot interoperate with FDO on v90. All that to say, a lot will depend on testing. If MapGuide moves to v100 and during testing, FDO proves not to be safe remaining on v90, then we will be forced to reconsider our position and consider moving as much of FDO and its providers to v100 as possible.
> 
> Regards,
> Greg
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
> Sent: Friday, April 01, 2011 4:16 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010
> 
> Hi Greg,
> 
> The GDAL extensions are available for both v90 and v100.  Basically we match the extensions to the build we are using.  If we have a v90 GDAL dll, then we would use v90 extensions.  If we move to a v100 GDAL dll then we would match it with v100 extensions.
> 
> If possible, it would be good to maintain a v90/v100 match between FDO and MapGuide.  There may be no issues using a v90 FDO with a v100 MapGuide.  I simply do not know.  In the past, we have always been in sync.  MapGuide and FDO do share the same process space so there is potential for unexpected behaviour.
> 
> Regards,
> Trevor
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> Sent: April 1, 2011 1:28 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010
> 
> Hi Trevor,
> 
> I agree that v100 versions of the GDAL binaries are available. However, we would need to port the FDO API, and its dependencies to v100. That would could ripple through the other providers, many of whom do not have v100 native SDKs available. While the OSGeo community is still discussing the matter, we have not yet decided to move FDO to v100. 
> 
> As for mixing runtimes for GDAL Provider and the GDAL extensions, (not being sure of how MapGuide is setup) who would be loading a v100 version of the GDAL extensions and in what content?
> 
> Greg
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
> Sent: Friday, April 01, 2011 2:24 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010
> 
> Hi Greg,
> 
> Mixing VC7 and VC9 binaries for the GDAL extensions caused the GDAL Provider to crash.  Using VC9 binaries for the extensions resolved the issue.
> 
> Prebuild GDAL binaries for VC2010 are available on http://vbkto.dyndns.org/sdk/.  It might be easier to use them directly.
> 
> Binaries for various flavours of linux are also listed on the website although I do not see RHEL 5 covered http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries
> 
> 
> Regards, 
> Trevor
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> Sent: April 1, 2011 12:03 PM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010
> 
> The OSGeo FDO project has no plans to port the GDAL Provider to the v100 runtime. 
> 
> What problems did you see and how are they related to the mixing of v90 and v100 runtimes?
> 
> Regards,
> Greg
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
> Sent: Friday, April 01, 2011 8:09 AM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] RE: Request Feedback: Support Vistual Studio 2010
> 
> Hello Mars,
> 
> We should only move MapGuide to Visual Studio 2010 if FDO is also moving to Visual Studio 2010.  I have seen unusual application behaviour with the FDO GDAL Provider in MapGuide when mismatched dlls are used.
> 
> Regards,
> Trevor
> 
> 
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Mars Wu
> Sent: March 30, 2011 8:21 PM
> To: MapGuide Internals Mail List (mapguide-internals at lists.osgeo.org)
> Subject: [mapguide-internals] Request Feedback: Support Vistual Studio 2010
> 
> Hi all,
> 
> I'd like to get your feedback about moving MapGuide to VS2010, both project files and compiler.
> 
> Bruce has posted a RFC last year about moving MapGuide to VS2010 project while keeping the code compiled with VS2008 compiler. http://trac.osgeo.org/mapguide/wiki/MapGuideRfc104
> This RFC was adopted but not yet completely implemented. Now a year has passed maybe we could move one step further to move MapGuide to also VS2010 compiler.
> 
> As the first step, we might keep the source code still compile with VS2008 and do some porting to make it also compile with VS2010 compiler. (The VS2008 project files are still available).
> 
> Could you share your feedback and concerns for this move? Is there any risk from your point of view (e.g. we already know some 3rd party components don't have VC10 built binaries)?
> 
> Thanks,
> Mars
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> 