<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>RE: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake Based</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That would be fine by me. I think the life of the sandbox could
be short lived here. I just think I need to get a sense of how the changes
would work.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Jason Birch<br>
<b>Sent:</b> Friday, November 28, 2008 10:30 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake
Based<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=idOWAReplyText14883>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>Hi Greg,</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I
don't know about you, but my time for meetings right now is pretty limited.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Would
you be happy going ahead with this in a sandbox, working out all of the issues
(making sure that the tests are run, passed as part of the build) to your
satisfaction, and then committing to trunk once it's working and we're all
happy with it? Although the changes would be non-intrusive,
this would Helio to make any required changes to the FDO code without
having to go through patch approval for each one, and it would keep the trunk
stable.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I
know I'm reversing my thinking on this one, but it does make sense.</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
</div>
<div id=idSignature54324>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>Jason</span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> fdo-internals-bounces@lists.osgeo.org on
behalf of Greg Boone<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake
Based</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p><span style='font-size:10.0pt'>Maybe we should have a PSC meeting to discuss
this issue? I would like to put this issue to bed.<br>
<br>
-----Original Message-----<br>
From: fdo-internals-bounces@lists.osgeo.org [<a
href="mailto:fdo-internals-bounces@lists.osgeo.org">mailto:fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Helio Chissini de Castro<br>
Sent: Wednesday, October 22, 2008 9:02 AM<br>
To: FDO Internals Mail List<br>
Subject: Re: [fdo-internals] FDO RFC 21 - New Linux Buildsystem Cmake Based<br>
<br>
On Terça 21 Outubro 2008 15:34:00 Jason Birch wrote:<br>
> 3) To my knowledge this process has only been run and tested against<br>
> Mandriva. I'll be happy to do the same against Ubuntu for sure, and
may<br>
> find time to set up VMs for Debian and a recent version of CentOS as<br>
> well. Helio, do you know if there is any intention of adding
MapGuide<br>
> support to the other GeoLinux distributions? Are there any problems<br>
> running the unit tests?<br>
<br>
Well, GeoLinux itself is a project started in Ecos to create global packages.<br>
At this moment, as exception for the Mapguide Live cd's, i didn't see any<br>
distro or gis based distro taken on mapguide. Is usually mapserver and mostly<br>
the Java stacks.<br>
I didn't made unit tests run just because i tried use external cppunit, but i<br>
will fall in use the ThirdParty one, as works only with that.<br>
<br>
> 4) Helio has taken on responsibility for maintaining the CMake build<br>
> process for GeoLinux (on Mandriva) and has done so for more than a year<br>
> in a consistent manner. I am personally willing to commit to
learning<br>
> CMake and helping to maintain it for FDO as well. Are either of
these<br>
> commitments as reliable as a full time paid position? Absolutely
not,<br>
> but I don't believe it is realistic to expect that from the open source<br>
> community.<br>
Yes, i just still not hapy to not been able to get rid of dbxml23 + xerces 2.7<br>
+ xqilla 1.0.1 + db 4.5 and can only work with that. Using db 4.6 cause<br>
headaches every new try.<br>
<br>
<br>
> BTW, I've been working with the CMake build process for MapGuide that<br>
> Helio just posted to the MapGuide-internals list. It seems simple
and<br>
> intuitive so far, in a way that I've never felt about the auto* chain.<br>
> If it is desired to have a mechanism to build using the included<br>
> libraries, it seems quite feasible to create something like the<br>
> build_linux.sh script that sets up the required command line options to<br>
> CMake.<br>
<br>
Is a text shell oriented script, even the tests are easy to do<br>
<br>
--<br>
Helio Chissini de Castro<br>
KDE Project<br>
Brasil and South America Primary Contact<br>
<br>
<br>
_______________________________________________<br>
fdo-internals mailing list<br>
fdo-internals@lists.osgeo.org<br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
_______________________________________________<br>
fdo-internals mailing list<br>
fdo-internals@lists.osgeo.org<br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a></span><o:p></o:p></p>
</div>
</div>
</body>
</html>