<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</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=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The idea for the version number is fine by me.<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As for a tag, we should tag …/branches/3.5 to -> …/tags/3.5_RC2.
When people are happy with RC2. We can tag …/tags/3.5_RC2 -> …/tags/3.5.0<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Greg<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 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> Saturday, September 18, 2010 1:42 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> Re: [fdo-internals] FDO 3.5 final release?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I like this idea a lot. <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>It's simple, doesn't require the amount
of additional work that tagging would, and means that for any build
you can go back to exactly the source that created it.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>We'll still require branches for major (3.5) releases, and
I'd suggest tags for minor (3.5.1) releases, though branches would be fine here
too if there's a requirement to release patches to minor releases.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Jason<o:p></o:p></p>
<div>
<p class=MsoNormal>On 18 September 2010 10:15, Trevor Wekel wrote:<o:p></o:p></p>
<p class=MsoNormal>Hmm... I had another idea for the FDO_VERSION and
PROVIDERS_VERSION tags. Why don't we just use the "Last Changed
Rev:" number from Subversion? This has a few advantages:<br>
<br>
* We can automate build number creation very easily using "svn info"
and some trivial perl scripting<br>
* We do not have to create tags for each build so there is less work involved<br>
* We always know exactly what version of the source we are dealing with<br>
* Each number in 3.5.0.0 corresponds to a 16 bit integer (0-65535) so we can use
the svn version number for a very long time.<br>
<br>
Here's the current "svn info" output for branches/3.5. This
would generate a build number of 3.5.0.5667 if we use the "Last Changed
Rev:" scheme.<br>
<br>
Path: 3.5<br>
URL: <a href="http://svn.osgeo.org/fdo/branches/3.5" target="_blank">http://svn.osgeo.org/fdo/branches/3.5</a><br>
Repository Root: <a href="http://svn.osgeo.org/fdo" target="_blank">http://svn.osgeo.org/fdo</a><br>
Repository UUID: d98eaee6-4212-0410-900c-dcc49bf69b99<br>
Revision: 5667<br>
Node Kind: directory<br>
Last Changed Author: trevorwekel<br>
Last Changed Rev: 5667<br>
Last Changed Date: 2010-09-17 16:57:10 -0600 (Fri, 17 Sep 2010)<br>
<br>
Regards,<br>
<span style='color:#888888'>Trevor</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Trevor Wekel<br>
Sent: September 18, 2010 9:11 AM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
Hi Greg,<br>
<br>
Ok. It looks like we have not created too many numeric tags for FDO 3.5
in <a href="http://trac.osgeo.org/fdo/browser/tags" target="_blank">http://trac.osgeo.org/fdo/browser/tags</a>.
Should we create a tag for RC2 build as 3.5_001 and set the FDO_VERSION
and PROVIDERS_VERSION to 0101?<br>
<br>
Regards,<br>
Trevor<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Greg Boone<br>
Sent: September 5, 2010 9:55 AM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
On a side note, I am not sure if you are setting these environment variables,
They will need to be set for a windows build.<br>
<br>
FDO_VERSION=xxxx<br>
PROVIDERS_VERSION=xxxx<br>
<br>
These variables are used to set the FDO binary version information.<br>
<br>
An example would be 6001. Where 60 is that build number (associated to the tag
number) and 01 would be the first iteration of build 60.<br>
<br>
Regards,<br>
Greg<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Trevor Wekel<br>
Sent: Saturday, September 04, 2010 10:43 AM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
Hi Greg,<br>
<br>
Ok. I will try the 32 bit build. I am still getting can't open file
.obj.rsp from boost when running the 64 bit build. Here are the commands
I am running on branches/3.5.<br>
<br>
svn export svn://localsvnrepo/fdo/branches/3.5 c:\builds\fdo35x64\fdo<br>
<br>
cd c:\builds\fdo35x64\fdo<br>
setenvironment.bat x64<br>
build_thirdparty.bat -p=x64 -a=buildinstall -o=c:\builds\fdo35x64\install<br>
<br>
<br>
One modification I did make to setenvironment.bat was to update the Visual
Studio path<br>
<br>
SET ACTIVEPATHCHECK="C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC"<br>
<br>
<br>
Regards,<br>
Trevor<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Greg Boone<br>
Sent: September 3, 2010 3:52 PM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
Hi Trevor,<br>
<br>
I tried building boost Win32 on a Win64 OS using the Visual Studio x86 compiler
tools and I didn't encounter any issues.<br>
<br>
Greg<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Trevor Wekel<br>
Sent: Tuesday, August 31, 2010 12:55 AM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
Hi Greg,<br>
<br>
I am able to build the following:<br>
<br>
Windows: MySQL, ODBC, PostgreSQL, GDAL, KingOracle, OGR, PostGIS, SDF, SHP,
SQLite, WFS, WMS<br>
<br>
Linux: MySQL, ODBC, PostgreSQL*, GDAL, KingOracle, OGR, PostGIS*, SDF, SHP,
SQLite, WFS, WMS<br>
<br>
*For Linux, I may have build issues with PostgreSQL and PostGIS related to the
Thirdparty pgsql libs. I get a number of unresolved externals for both
providers and need to investigate further.<br>
<br>
<br>
Regards,<br>
Trevor<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Greg Boone<br>
Sent: August 30, 2010 10:07 PM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
Trevor,<br>
<br>
What builds (minus ArcSDE) are you capable of posting? Why don't we focus on
posting what you can build right now.<br>
<br>
I can work on posting the ArcSDE libraries once you have posted the main build.
I can also look to see if I can reproduce the boost x86 issue so you can
perform the win32 build on your win64 machine.<br>
<br>
As for testing, I propose we post and have the community validate.<br>
<br>
Greg<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Greg Boone<br>
Sent: Monday, August 30, 2010 11:34 PM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
So a number of submissions have been made lately. Are there any objections to
having these included in a new candidate build?<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Trevor Wekel<br>
Sent: Saturday, August 28, 2010 12:35 PM<br>
To: FDO Internals Mail List<br>
Subject: RE: [fdo-internals] FDO 3.5 final release?<br>
<br>
Hi Jackie,<br>
<br>
Your question is timely. I have been discussing the FDO builds offline
with Greg and others over the past few months. Since MapGuide needs FDO
for Windows and Linux, I thought it was reasonable for me to do the FDO builds
as well. I believe there are a few things we need to address:<br>
<br>
1. Build OS for Windows<br>
<br>
Currently, the FDO 3.5 builds are cleaner on a 32 bit OS. From what I
recall, one of the third party dependencies (boost?) is a bit out of date and
gets a little cranky with the (x86) in the path name. I believe this has
been resolved in FDO trunk. The 32/64 bit OS wouldn't normally matter
but I was foolish enough to install a 64 bit OS on the MapGuide build machine.<br>
<br>
We have a couple of options available to resolve this:<br>
a. Set up a separate build VM for FDO with a 32 bit OS.<br>
b. Update the third party libs and compile using the existing MapGuide 64
bit build VM.<br>
<br>
Option a. is cleaner and I think it would be better if FDO had its own build
machine. I suppose I can eat the licensing cost (bummer).<br>
<br>
<br>
2. ArcSDE Providers<br>
<br>
I do not have access to ESRI SDKs so I cannot build the ESRI FDO Providers.
If someone else in the community would be willing to build the ESRI
Providers, that would be great.<br>
<br>
<br>
3. Resourcing<br>
<br>
To be honest, I am very busy right now and would welcome a collaborator on the
FDO builds. The build infrastructure is web accessible and I would be
more than willing to give access to anyone able to help out with the FDO
builds.<br>
<br>
<br>
4. Build Validation<br>
<br>
I am competent in FDO but not an FDO expert. And with 10(+?) providers to
test, build validation is a major undertaking. We should open up a
discussion on appropriate build validation steps. Builds are fine.
Builds that work are better.<br>
<br>
<br>
Regards,<br>
Trevor<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>
[mailto:<a href="mailto:fdo-internals-bounces@lists.osgeo.org" target="_blank">fdo-internals-bounces@lists.osgeo.org</a>]
On Behalf Of Jackie Ng<br>
Sent: August 28, 2010 2:45 AM<br>
To: <a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
Subject: [fdo-internals] FDO 3.5 final release?<br>
<br>
<br>
Hi All,<br>
<br>
Is there any word/plans on a final FDO 3.5 release? The download site only has
the RC1 release and that itself is several months old now.<br>
<br>
- Jackie<br>
--<br>
View this message in context: <a
href="http://osgeo-org.1803224.n2.nabble.com/FDO-3-5-final-release-tp5472205p5472205.html"
target="_blank">http://osgeo-org.1803224.n2.nabble.com/FDO-3-5-final-release-tp5472205p5472205.html</a><br>
Sent from the FDO Internals mailing list archive at Nabble.com.<br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
<br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
<br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
<br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
fdo-internals mailing list<br>
<a href="mailto:fdo-internals@lists.osgeo.org" target="_blank">fdo-internals@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</body>
</html>