Jürgen --
The problems are mostly with linking compiled C++
code. Due to the different name mangling schemes,
a DLL produced by VC might not be usable by
an EXE produced with MinGW and vice versa.
There are tools to work around that:
http://www.mingw.org/wiki/MSVC_and_MinGW_DLLs
I have tried and it works -- sometimes.
Anyway, it's a wasted effort for me, as I prefer
to fix source code and configure files so that
everything compiles cleanly using MinGW.
Why should using the C standard lib's free() a bug?
Cheers,
Ben
On 11/05/2012 12:38 AM, Jürgen E. Fischer wrote:
Hi Ben,
On Sun, 04. Nov 2012 at 23:32:41 +0100, Benjamin Ducke wrote:
Indeed: MinGW and VC DLLs do not mix well,
In what way?
An important thing is to use the right function to release memory (G_free(),
GEOSFree(), CPLFree()...). Simply using free() might crash on windows, but
that IMHO should be considered a bug anyway.
Jürgen
--
Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer
[email protected]
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
