It seems like OSGeo4W is made out of several heterogenous compilers. I'm
surprised there is so little (not a single ?) "runtime library
incompatibility hell"...
oh dll hell has shown it's face around here alright. :)
That's why Frank built dllupdate
(http://trac.osgeo.org/osgeo4w/wiki/dllupdate).
DLL hell - piece of cake ;)
I think Julien is more after more subtle cases like:
http://trac.osgeo.org/osgeo4w/ticket/40
http://trac.osgeo.org/osgeo4w/ticket/68
http://trac.osgeo.org/qgis/ticket/3766
Just to name a few. There were many more.
Hummm... Delightful moments...
There is the memory freeing problem as you mentioned.
I also remember a good one about FILE* fopen'ed in one lib and fclose'd
in another one (with curl and jpeg, both providing a way out).
Julien
_______________________________________________
osgeo4w-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
