[mapguide-internals] MapGuide RFC 57 - Refining the linux buildprocess and generating install packages

Jason Birch Jason.Birch at nanaimo.ca
Wed Nov 26 01:06:47 EST 2008


 
Thanks for putting that together Zac.
 
I'm not sure which OEM components have been modified specifically for MapGuide.  I'm pretty sure that AGG has been, and we have to make sure that we only bundle the older 2.4 version with any releases that we do to avoid contaminating our code with GPL.  Are there any other OEM components that have modifications that haven't been contributed/adopted upstream?  I see that at least GEOS and GD (libpng) have had some code modifications made to support 64 bit compilation.
 
Tom, I'd agree that the Windows build process is easy, but maybe too easy  :)   I'd love to try swapping out some of the OEM components in the Windows build/packages for 2.1, especially Apache, PHP, and GEOS.  Unfortunately, I think that this may be a bit optimistic given that some packages (such as ACE) haven't been updated in over four years, and I don't have the developer chops to fix anything I run into.
 
Jason

________________________________

From: mapguide-internals-bounces at lists.osgeo.org on behalf of Zac Spitzer
Sent: Tue 2008-11-25 6:50 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] MapGuide RFC 57 - Refining the linux buildprocess and generating install packages



Following up on the various discussions about the linux build process
I have created a draft RFC
for refining the linux build process and generating install packages.

http://trac.osgeo.org/mapguide/wiki/MapGuideRfc57

z

--
Zac Spitzer -
http://zacster.blogspot.com <http://zacster.blogspot.com/> 
+61 405 847 168
_______________________________________________
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