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

[Haris Kurtagic]

Thanks Andy, that sounds good. So, we can more easily build different
version of MG.
Haris


On Tue, Jun 4, 2013 at 3:04 AM, Andy Zhang <Andy.Zhang at autodesk.com> wrote:

> Hi Haris,
>
> Yes. I also prefer to use configuration macro. So for ServerCore, the
> intermediate directory will be
> ..\..\obj\$(PlatformToolset)\$(Configuration)\ServerCore.
>
> I updated RFC 135 to add this line. Please review.
> *We will add configurations such as 'Release v100' and 'Debug v100' which
> use platform toolset v100 for those who need to build v100 versions of
> files. And the project properties for output, intermediate and lib
> directories will include $(PlatformToolset) and $(Configuration) macros.
> Example: the intermediate directory of ServerCore will be changed to
> ..\..\obj\$(PlatformToolset)\$(Configuration)\ServerCore.
>
> Best Regards
> Andy
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris Kurtagic
> Sent: Monday, June 03, 2013 6:01 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] RFC 135: Support Visual Studio 2012
>
> Hi Andy,
>
> thanks for adding to RFC. I am not sure from the text in RFC, it would be
> good to have in project properties for output, intermediate and lib
> directory to include $(PlatformToolset) macro so insetad of (MG 2.2 )
>  ..\..\obj\release64\ServerCore to have like
> ..\..\obj\$(PlatformToolset)\release64\ServerCore
> btw, personally i would also like to have instead of release configuration
> macro etc..
>
> Haris
>
>
> On Mon, Jun 3, 2013 at 8:41 AM, Andy Zhang <Andy.Zhang at autodesk.com>
> wrote:
>
> > Hi Haris,
> >
> > Thanks for your reply.
> > I updated the RFC to add the line below.
> > * We will add configurations such as 'Release v100' and 'Debug v100'
> > which use platform toolset v100 for those who need to build v100
> > versions of files.
> >
> > Are we ready for vote?
> >
> > Best Regards
> > Andy
> >
> > -----Original Message-----
> > From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> > mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris
> > Kurtagic
> > Sent: Sunday, June 02, 2013 6:34 AM
> > To: MapGuide Internals Mail List
> > Subject: Re: [mapguide-internals] RFC 135: Support Visual Studio 2012
> >
> > Hi Andy,
> > Sorry for late response, I was a offline for couple of days.
> >
> > It would be great if initially it would build in previous VS compiler
> > versions too. I guess we could get benefits of moving  to use new
> > Studio and still doesn't need to do immediately support new compiler
> versions.
> >
> > I believe one small thing, but important when comes to using solution
> > and project, is to setup such configuration properties for directories
> > (Output,Bin, Lib ..) so it includes platform toolset so it would be
> > able to support different compiler builds
> >
> > Haris
> >
> >
> > On Fri, May 31, 2013 at 7:06 AM, Andy Zhang <Andy.Zhang at autodesk.com>
> > wrote:
> >
> > > Hi Haris,
> > >
> > > >>>>We could use "Platfrom Toolset" project configuration option to
> > > achieve that.
> > > Could you please provide more detail about this? In my VS2012, we
> > > can select several platform toolsets including VS2010(v100),
> > > VS2012(v110) in project properties page. Do you mean we need to make
> > > the projects built successfully when we select VS2010(v100)?
> > >
> > > Thanks
> > > Andy
> > >
> > > -----Original Message-----
> > > From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> > > mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris
> > > Kurtagic
> > > Sent: Friday, May 31, 2013 6:42 AM
> > > To: MapGuide Internals Mail List
> > > Subject: Re: [mapguide-internals] RFC 135: Support Visual Studio
> > > 2012
> > >
> > > Hi,
> > > is it possible that even if we move to 2012 project/solution files,
> > > we keep configurations for 2010 ? We could use "Platfrom Toolset"
> > > project configuration option to achieve that.
> > >
> > > I am currently using this approach for my FDO builds, where I need
> > > to build different versions of libs. Having different project files
> > > for different studio builds is huge overhead.
> > > I am also extensively using property sheets, for easy customization
> > > of the configuration builds.
> > >
> > > Haris
> > >
> > >
> > > On Thu, May 30, 2013 at 2:50 PM, 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-
> > > > 20
> > > > 12 -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
> > > >
> > > _______________________________________________
> > > 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
> >
> _______________________________________________
> 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
>