[mapguide-internals] RFC 135: Support Visual Studio 2012

Mars Wu mars.wu at autodesk.com
Thu May 30 05:50:42 PDT 2013


Previously, we did the upgrades (for PHP etc.) in a separate RFC. It happened that php binaries in MapGuide are built from different version of VC. It seems there is no cross-dll memory allocation and release so it should be safe to leave PHP built with VC10 and just upgrade MapGuide to VS12 first. 

Thanks,
Mars 

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Thursday, May 30, 2013 10:22 AM
To: mapguide-internals at lists.osgeo.org
Subject: Re: [mapguide-internals] RFC 135: Support Visual Studio 2012

Just occurred to me. I believe the binaries we're keeping under Oem\php\Release_TS and Oem\php\x64\Release_TS are VS2010 built ones.

Will we require VS2012 built copies of Apache and PHP as well as part of this RFC?

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/RFC-135-Support-Visual-Studio-2012-tp5053832p5056855.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


More information about the mapguide-internals mailing list