[mapguide-internals] Patch: Remove usage of DbXml private header

[Traian Stanev]

> Is there something really special inside mapguide gd that i miss ?

Yes.

With the external gd, you will find that labeling of polylines will not
work. Text in general may not draw at all. Also, if you use tiled maps,
there will be discontinuities across tile boundaries. I am not sure if
the other bug we fixed was also fixed in the main gd stream, it had to
do with crashes because pixels outside the image were accessed by the
antialiased line drawing algorithm. There was also a bug in GIF output
that I am not sure was fixed in the main stream. I guess I should check
up on that, but considering how little time I have it probably won't
happen soon...

When I last tried an x64 build, the MapGuide server would crash on
startup. Have you seen such problems?


Traian


-----Original Message-----
From: Helio Chissini de Castro [mailto:helio at kde.org] 
Sent: Friday, May 11, 2007 3:23 PM
To: mapguide-internals at lists.osgeo.org
Cc: Traian Stanev
Subject: Re: [mapguide-internals] Patch: Remove usage of DbXml private
header

Em ven 11 mai 2007, Traian Stanev escreveu:
> Hi Helio,
>
> Just for information (so that you don't get a nasty surprise),
compiling
> against external versions of the libraries is fine, except for gd. For
gd
> you should use the source provided by MapGuide. It's ok to use
external
> libraries for all of gd's dependencies (jpeg, png, freetype2, etc). I
> recently did a build on the newest Ubuntu and I also used a mix and
match
> of external libraries (in particular I used the libACE that was
available
> on the machine, since the one that came with MapGuide was not
compiling for
> some reason).
>
> Traian

Ok, so i need disclose more info :-)

I already compiled full mapguide on purpose to create an RPM ( Mandriva
in my 
case ). I had the problem on the old gd, ( several crashes ) but now the

current version that i'm using with patches are ok. Is there something
really 
special inside mapguide gd that i miss ?
I'm using just SWIGEx internal.
As external deps, i'm using:
db-4.3.29, dbxml-2.2.13, ace-5.5.2, gd-2.0.34, xalan-c-1.10,
xerces-c-2.7.0, 
php-5.2.2.
I created packages for fdo and libdwf as well.
My nightmare was just libdwf, when compiling against x86_64. Mapguide
itself 
have some c++ issues with types during compilation, like have places
where 
function in defined as long long int in header, but implementation is
using 
FdoInt64, which compiles fine on i586, but breakes compilation in gcc
x86_64.

Due my background as kde devel, i really hate from the deep of my heart 
auto*tools, then i keep all mapguide source in sync, but recreated
entire 
mapguide buildsystem using CMake for the rpm purpose
Is completly working, and i would love to share if have someone
interested. 
CMake is "really" multiplatform, easy to manage, full textfile without
stange 
macros, and thanks God, reduce the size of tests tools and maintenance 
burden. My current buildsystem is *nix only, but with a little work, can
be 
added to build on Mac and Windows as well, with one only buildsystem.
JFYI, even i needed to resync every new mapguide release, i prefer 10
times 
work this way than using auto*tools again.

Hope i get things more clear.

[]'s

-- 
Helio Chissini de Castro
KDE Project South America Primary Contact
Curitiba - Brasil