[fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake Based

[Jason Birch]

I think numbers 1, 2, and 5 have been addressed.  (it won't modify the
existing process; no impact on the Windows build; won't give us a
buildbot).  I'll note that Trevor W. is working on a continuous build
process for MapGuide Open Source on his personal servers; perhaps there
is an opportunity for FDO to piggyback on that with some kind of
resource contribution?

I see the rest of the questions as appropriate if this were to be the
sole build mechanism for FDO, but as an alternate build procedure I
don't understand why this level of rigour needs to be applied.  The
point of getting the scripts into the SVN repository is so that the
community can more easily access the CMake build, keep it maintained,
and start to develop process around it.  If your requirements (unit
tests and documentation) don't happen organically, then the CMake build
process can be declared a failure and removed with no ill effects.  I
personally think that expecting new features to spring to life
fully-formed from an open source community is unrealistic, and applying
commercial development constraints to this project will ultimately limit
FDO as an open source project; Autodesk and consultants such as SL-King
will be the only ones able to contribute effectively.

Here's my take at answering the outstanding questions:

3) To my knowledge this process has only been run and tested against
Mandriva.  I'll be happy to do the same against Ubuntu for sure, and may
find time to set up VMs for Debian and a recent version of CentOS as
well.  Helio, do you know if there is any intention of adding MapGuide
support to the other GeoLinux distributions?  Are there any problems
running the unit tests?

4) Helio has taken on responsibility for maintaining the CMake build
process for GeoLinux (on Mandriva) and has done so for more than a year
in a consistent manner.  I am personally willing to commit to learning
CMake and helping to maintain it for FDO as well.  Are either of these
commitments as reliable as a full time paid position?  Absolutely not,
but I don't believe it is realistic to expect that from the open source
community.

6) I will take on documenting this process, once the code is available
in SVN.  I'm sure others will contribute, as they have to the MapGuide
quick start guides on the OSGeo wiki.

BTW, I've been working with the CMake build process for MapGuide that
Helio just posted to the MapGuide-internals list.  It seems simple and
intuitive so far, in a way that I've never felt about the auto* chain.
If it is desired to have a mechanism to build using the included
libraries, it seems quite feasible to create something like the
build_linux.sh script that sets up the required command line options to
CMake.

Jason

-----Original Message-----
From: Greg Boone
Subject: RE: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake
Based

Clarification:

3) How has the build and the resulting FDO binaries been tested and on
which platforms has they been tested? What are the output test results?

Additional Question:

6) Where is the build/runtime document that explains how to execute the
new build process and validate the result of the build using the FDO
unit tests?

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Monday, October 20, 2008 4:25 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake
Based

I believe I asked these questions before, but if these new files are
submitted

1) Will it modify the existing build process?
2) How will it integrate with the current Windows build process?
3) How has it been tested and on which platforms has it been tested?
4) Who will maintain and support these files and this build process
going forward? Someone needs to be tasked with this responsibility.
5) Will we finally get a buildbot setup if we move to this process?

All these questions need to be answered to my satisfaction, and in
detail, before I would consider approving this RFC.

Greg

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Frank
Warmerdam (External)
Sent: Monday, October 20, 2008 3:09 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake
Based

Jason Birch wrote:
> I think that this was the last of the questions?
>
> Rather than continuing to beat this to death, I would really like to
> see:
>
> - Helio's current (3.4.x) cmake work checked into trunk as an
alternate
> build system
> - With the understanding that this is Linux-only (and BSD/MacOS as we
> have time); won't touch Windows solutions, etc at all

Jason,

I think the way forward is to update RFC 21 to handle your proposed
transitional approach, and then call for a vote on it.

At this point I'm moderately supportive of the approach, and will commit
to doing at least some testing of the new build mechanism once it is in
place.

I would like to see the RFC include an action item for someone to write
up a brief introduction to using and updating cmake in the context of
FDO.

Best regards,
--
---------------------------------------+--------------------------------
------
I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals