[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fdo-internals
Subject:    [fdo-internals] RE: FDO 3.6 Release Candidate and Branching
From:       Traian Stanev <traian.stanev () autodesk ! com>
Date:       2011-01-27 18:16:24
Message-ID: 0D757A4B577F7E42B5166013D347B6DA14F18A26 () 005-TK5MPN1-002 ! MGDADSK ! autodesk ! com
[Download RAW message or body]

Hi Trevor,

I have used the SHP, OGR and SQlite providers on Linux/64. The only issues =
I had were with the SHP provider using incorrect alignment in some structur=
es, but I fixed those when I found them. As far as building with the latest=
 Gcc, it might require a minor amount of coaxing to get it to compile, but =
I don't expect it to be anything major.

Traian

P.S. I was using the CMake build and all third party components were the on=
es installed by apt-get rather than the ones that come with FDO itself. Sin=
ce recently, this is no longer possible as Xalan 1.1 is not compatible with=
 Xerces 3 as distributed by the Ubuntu repositories, while FDO no longer co=
mpiles with older the Xerces.


From: fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@l=
ists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Thursday, January 27, 2011 12:41 PM
To: FDO Internals Mail List
Cc: FDO Users Mail List (fdo-users@lists.osgeo.org)
Subject: [fdo-internals] RE: FDO 3.6 Release Candidate and Branching

Hi Greg,

I'm curious to know if anyone has  tried 64 bit compilation and gcc 4.4 com=
pilation of FDO on Linux.  MapGuide currently has 64 bit support for Window=
s but not for Linux.  And it would be good get to MapGuide and FDO compilin=
g on Ubuntu 10.04 LTS which uses gcc 4.4.

Regards,
Trevor

From: fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@l=
ists.osgeo.org] On Behalf Of Greg Boone
Sent: January 26, 2011 2:05 PM
To: FDO Internals Mail List (fdo-internals@lists.osgeo.org)
Cc: FDO Users Mail List (fdo-users@lists.osgeo.org)
Subject: [fdo-internals] FDO 3.6 Release Candidate and Branching

Hi All,

It is getting to that time of year that we typically branch FDO in preparat=
ion for a full FDO release (3.6), allowing the trunk to continue on as a fu=
lly-open development environment leading towards the next iteration of FDO,=
 namely 3.7.

In conjunction with that happening, I was thinking to post an official Rele=
ase Candidate of FDO and create a 3.6 branch under:

https://svn.osgeo.org/fdo/branches/3.6

Are there any concerns with branching FDO at this time or releasing a candi=
date build?

Regards,
Greg

[Attachment #3 (text/html)]

<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 14 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'>Hi Trevor,<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'>I have used the SHP, OGR and SQlite providers on Linux/64. The \
only issues I had were with the SHP provider using incorrect alignment in some \
structures, but I fixed those when I found them. As far as building with the latest \
Gcc, it might require a minor amount of coaxing to get it to compile, but I \
don&#8217;t expect it to be anything major.<o:p></o:p></span></p><p \
class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal><span style='color:#1F497D'>Traian<o:p></o:p></span></p><p \
class=MsoNormal><span style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p \
class=MsoNormal><span style='color:#1F497D'>P.S. I was using the CMake build and all \
third party components were the ones installed by apt-get rather than the ones that \
come with FDO itself. Since recently, this is no longer possible as Xalan 1.1 is not \
compatible with Xerces 3 as distributed by the Ubuntu repositories, while FDO no \
longer compiles with older the Xerces.<o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span \
style='color:#1F497D'><o:p>&nbsp;</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>Trevor Wekel<br><b>Sent:</b> Thursday, January 27, 2011 12:41 \
PM<br><b>To:</b> FDO Internals Mail List<br><b>Cc:</b> FDO Users Mail List \
(fdo-users@lists.osgeo.org)<br><b>Subject:</b> [fdo-internals] RE: FDO 3.6 Release \
Candidate and Branching<o:p></o:p></span></p></div></div><p \
class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><span lang=EN-CA \
style='color:#1F497D'>Hi Greg,<o:p></o:p></span></p><p class=MsoNormal><span \
lang=EN-CA style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span \
lang=EN-CA style='color:#1F497D'>I&#8217;m curious to know if anyone has&nbsp; tried \
64 bit compilation and gcc 4.4 compilation of FDO on Linux.&nbsp; MapGuide currently \
has 64 bit support for Windows but not for Linux.&nbsp; And it would be good get to \
MapGuide and FDO compiling on Ubuntu 10.04 LTS which uses gcc \
4.4.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA \
style='color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-CA \
style='color:#1F497D'>Regards,<o:p></o:p></span></p><div><p class=MsoNormal><span \
lang=EN-CA style='color:#1F497D'>Trevor<o:p></o:p></span></p></div><p \
class=MsoNormal><span lang=EN-CA \
style='color:#1F497D'><o:p>&nbsp;</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>Greg Boone<br><b>Sent:</b> January 26, 2011 2:05 PM<br><b>To:</b> \
FDO Internals Mail List (fdo-internals@lists.osgeo.org)<br><b>Cc:</b> FDO Users Mail \
List (fdo-users@lists.osgeo.org)<br><b>Subject:</b> [fdo-internals] FDO 3.6 Release \
Candidate and Branching<o:p></o:p></span></p></div></div><p class=MsoNormal><span \
lang=EN-CA><o:p>&nbsp;</o:p></span></p><p class=MsoNormal>Hi All,<o:p></o:p></p><p \
class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>It is getting to that time of \
year that we typically branch FDO in preparation for a full FDO release (3.6), \
allowing the trunk to continue on as a fully-open development environment leading \
towards the next iteration of FDO, namely 3.7. <o:p></o:p></p><p \
class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>In conjunction with that \
happening, I was thinking to post an official Release Candidate of FDO and create a \
3.6 branch under:<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p \
class=MsoNormal style='text-indent:.5in'><a \
href="https://svn.osgeo.org/fdo/branches/3.6">https://svn.osgeo.org/fdo/branches/3.6</a><o:p></o:p></p><p \
class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
<o:p></o:p></p><p class=MsoNormal>Are there any concerns with branching FDO at this \
time or releasing a candidate build?<o:p></o:p></p><p \
class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p \
class=MsoNormal>Greg<o:p></o:p></p></div></body></html>



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

--===============1167279012==--

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic