[mapguide-internals] Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

Andy Zhang Andy.Zhang at autodesk.com
Thu May 28 17:37:26 PDT 2015

Hi Jackie,

Fusion and CsMap are in Oem folder now. Will they be moved to the separate OEM folder too?
Best Regards

-----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 28, 2015 10:48 AM
To: mapguide-internals at lists.osgeo.org
Subject: Re: [mapguide-internals] Review/Discuss: MapGuide RFC 149 (Lightweight MapGuide Source Tree)

The main motivation for this RFC is to make the MapGuide codebase more conductive to agile development, rapid iteration and continuous integration.

It's very hard to rapidly iterate on MapGuide when you have nearly 2GB of source code to check out and 2-3hrs build time for each build run.

So while yes, this does stunt the open-in-VS-and-compile experience for beginners, it's a small price to pay for faster build cycles.

I'd also argue that this new build process isn't much more different than what is currently in FDO. In FDO you had to init the build environment first with setenvironment.[bat|sh] before you could build from the command line or open up any FDO project in VS to build/debug. It wouldn't be that much different here.

- Jackie

View this message in context: http://osgeo-org.1560.x6.nabble.com/Review-Discuss-MapGuide-RFC-149-Lightweight-MapGuide-Source-Tree-tp5207824p5207909.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org

More information about the mapguide-internals mailing list