[fdo-internals] FDO 3.5 final release?

[Greg Boone]

Trevor,

What builds (minus ArcSDE) are you capable of posting? Why don't we focus on posting what you can build right now. 

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. 

As for testing, I propose we post and have the community validate. 

Greg

-----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, August 30, 2010 11:34 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO 3.5 final release?

So a number of submissions have been made lately. Are there any objections to having these included in a new candidate build?

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Saturday, August 28, 2010 12:35 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO 3.5 final release?

Hi Jackie,

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:

1.  Build OS for Windows

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.

We have a couple of options available to resolve this:
a.  Set up a separate build VM for FDO with a 32 bit OS.
b.  Update the third party libs and compile using the existing MapGuide 64 bit build VM.

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).


2. ArcSDE Providers

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.


3. Resourcing

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.


4. Build Validation

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.


Regards,
Trevor

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: August 28, 2010 2:45 AM
To: fdo-internals at lists.osgeo.org
Subject: [fdo-internals] FDO 3.5 final release?


Hi All,

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.

- Jackie
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/FDO-3-5-final-release-tp5472205p5472205.html
Sent from the FDO Internals mailing list archive at Nabble.com.
_______________________________________________
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