[mapguide-internals] MapGuide Open Source 2.1
Jason.Birch at nanaimo.ca
Thu Oct 16 15:21:38 EDT 2008
I know that this isn't a solution for the Windows builds, but the work
that Helio did with cmake for the Linux builds removed the majority of
the dependencies on the bundled OEM packages, so at least we know that
MapGuide runs on newer versions of the libraries on Linux.
Part of the solution could be to adopt Helio's cmake-based build process
for MapGuide (and FDO). Adopting this would likely be less work than
fixing the existing Linux process and, to me at least, the cmake setup
is much more transparent than the autotools stuff. I know that there
are others with different opinions, but have a look at Traian's
cmake-based build scripts (CMakeLists.txt) for the SQLite provider:
I'm not sure what the answer would be for Windows though... an
environmental variable set for each library that could be referenced in
From: Tom Fukushima
Subject: RE: [mapguide-internals] MapGuide Open Source 2.1
This has been bothering me a bit as well.
Can someone explain why we have taken the approach we did and what the
plans are for OEM going forward? I don't know the history of this.
Bruce and Trevor?
More information about the mapguide-internals