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

[Trevor Wekel]

I suspect Apache and PHP will also require VS2012 recompilation.  I
agree with Mars that these should be handled in separate RFCs.
Upgrading the versions of Apache and PHP may be required to get "easy"
VS2012 support.

The easiest way to confirm is to do the MapGuide upgrade first.

Perhaps we should write a note in RFC 135 regarding potential
Apache/PHP RFCs for VS2012 recompilation?

I am ok with RFC 135.

Are we ready to vote?




On 2013-05-30, at 6:49 AM, Mars Wu <mars.wu at autodesk.com> wrote:

> 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
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals