[mapguide-internals] MapGuide open source builds
trevor.wekel at autodesk.com
Wed Oct 8 14:39:32 EDT 2008
To build on Windows, we need compilation support for both C++ and .Net. We may be able to install both the Visual Studio 2008 Express Edition for C++ and Express Edition for .Net to get the required compilation support. There may also be pieces missing from the 2008 Express Editions which we would need to install separately such as the Platform SDK.
Please keep in mind we already have an effective build process for Windows using Visual Studio solution and project files. This also makes it easier to debug MapGuide using Visual Studio 2008. Personally as a developer, I would be a little grumpy if we dumped this. As far as I am concerned, Visual Studio is still the best development/debugging environment out there for the Windows platform.
Based on Jason's original suggestions, I did a little research into NSIS. For packaging MapGuide, I think it will work. One thing I did notice is that NSIS does not seem to support direct modification of the IIS metabase. If we want the Web Extensions installer to correctly register MapGuide under IIS, we may need to write some custom code. Microsoft .Net does have API for modifying the metabase so we could write a custom .Net dll for this portion of the install.
Or alternatively, we could just use Visual Studio Standard Edition. It bundles C++ and .Net support and comes with installer projects suitable for MapGuide. The installer projects support web deployment. From what I understand, you get a nice GUI tree for your virtual directory structure, and you can add application mappings through the UI. It looks dirt easy.
The full product comparison for the various Visual Studio versions is available here http://msdn.microsoft.com/en-us/vs2008/products/cc149003.aspx. For the most part, there is not a huge difference between the Standard and Professional versions. Visual Studio Standard edition costs about $340 CDN. If we go with this approach, anyone wanting to work on the installers would need to purchase Visual Studio Standard. Anyone just doing regular development should be able to get away with the Express Editions.
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Traian Stanev
Sent: Wednesday, October 08, 2008 10:22 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] MapGuide open source builds
Yes, I did a 64 bit FDO build using externally installed dependent third party libraries last week on Ubuntu, and it worked out pretty well. I did not compile all providers though, so I can't speak for all the dependencies, just xerces/xalan and the like.
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-
> internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
> Sent: Wednesday, October 08, 2008 12:16 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] MapGuide open source builds
> reading the thread, the last post even mentioned a working rpm
> distribution mechanism
> other items i skimmed out was that getting rid of most of the
> thirdparty directory provides much
> better 64-bit support, and the compile time is meant to be a lot
> faster... ie less than 10 hours
> or so from memory
> the major issue seemed to be whether it was windows & linux or just
> and the generation of the visual studio build files via cmake wasn't
> too popular
> On Thu, Oct 9, 2008 at 3:06 AM, Jason Birch <Jason.Birch at nanaimo.ca>
> > I don't think it even made it to RFC for MapGuide, though it did for
> FDO. But then the FDO RFC got mired in Q&A. A bit of a frustrating
> experience for me (and I think probably for Helio as well) given the
> current difficulty of building FDO/MapGuide across various Linux
> platforms _and_ the fact that the build was ready to go and just had to
> be adopted as an alternate build system.
> > Jason
> > -----Original Message-----
> > From: Traian Stanev
> > Subject: RE: [mapguide-internals] MapGuide open source builds
> > Someone (Helio...) implemented a cmake build system for FDO and
> MapGuide recently, with all the external dependencies sorted out. As
> far as I remember, it didn't make it past the RFC stage, but you may be
> able to get a hold of his cmake files to try out.
> > _______________________________________________
> > mapguide-internals mailing list
> > mapguide-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> Zac Spitzer -
> http://zacster.blogspot.com (My Blog)
> +61 405 847 168
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals