Easier to compile?  Yes.  The libraries will be up to date.

Easier to ensure MapGuide stability?  That's a very good question.  Mixing and 
matching oem libs could potentially lead to unexpected side effects but more up 
to date libraries *should* have fewer bugs.

Regards,
Trevor

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Zac Spitzer
Sent: March 31, 2010 5:50 PM
To: MapGuide Users Mail List
Subject: Re: [mapguide-users] building 64bit openmapguide on rhel 5.4

migrating away from using all these third party libs in the oem tree
on linux and use the system ones when possible is a better approach

On 1 April 2010 10:34, Trevor Wekel <[email protected]> wrote:
> Hi Rajeev,
>
> Third party components can be very tricky business in MapGuide.  For example, 
> Berkeley DB XML uses specific versions of xerces and xalan.  These three 
> third party libraries should remain in sync to ensure repository stability.  
> In order to compile with GCC 4.4, we will need to update a significant 
> portion of the Oem tree.  Since we are about to hit beta, I would say any 
> additional changes to third party / Oem libraries would have to be considered 
> on a case by case basis.
>
> Hopefully our existing set of third party libs will compile successfully on 
> 64 bit Linux.  If not,  RFC's will have to be written to get the libraries 
> upgraded.  For example, RFC 89 
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc89 was a required upgrade for 
> 2.2.
>
> As for source code modifications, yes there have been a few 
> (geos,swig,agg,others?).  I do not know if the modifications have made it 
> back into their respective projects.
>
> Regards,
> Trevor
>
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Rajeev Singh
> Sent: March 31, 2010 7:02 AM
> To: MapGuide Users Mail List
> Subject: RE: [mapguide-users] building 64bit openmapguide on rhel 5.4
>
> Hi Trevor,
>
> I will certainly look into this - though adam probably will get to it
> sooner. Right now finally gotten around to looking at 32 bit crash of 2.0.2
> branch (had filed a bug earlier, essentially every 1/2 hr or so the process
> crashes).
>
> As an aside, when going thru the attempt on 2.0.2, I did complie FDO 3.3.2
> on 64 bit (compiled  all except a few dealing with ODBC/PostGis/Oracle, but
> including MySQL)
>
> On a different note, lots of third party components are used with mapguide.
> At some point I think I had seen in some mailing list that the source code
> have been modified. Is that really so or can we instead create a packaging
> that uses the latest / required binaries of those components (I can help
> with that)
>
> thanks
> rajeev
>
> _______________________________________________
> mapguide-users mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users


_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Reply via email to