Re: Patches to compile CC++ 2 for Win32 with GCC using Mingw32

[Federico Montesino Pouzols]

> I like this patch.  I gather you have been able to build libxml2 and
> libiconv  as well (perhaps as dll's) with the debian mingw32 tool chain?
>

   Yes, they all can be built with gcc-mingw32. And there is more: with
just a few #ifdefs, libxml2 and other libraries (for instance oSIP) can
be built out of the source tarball with the usual ./configure; make.
However I have not been able to build dll's with autotools; libtool seems
to get messed. What I am doing is to build the static library (and the
demo apps with the autotools) and the dll manually.

   With common c++ the autotools' makefiles does not seem to be correctly
generated when I use the cross gcc. So I have built cc++ with the
Makefile.gcc. Do you know if there is something in the autoconf stuff of
cc++ that may break with cross compilers? If not, I will have to look at
the Makefiles and try to find the problem...

> My other thought is maybe we should have the mingw32 makefile build two
> seperate and dependent dll's (ccgnu and ccstd) the way the normal build
> tree  does for posix targets.
>

    Ok, building ccgnu2.dll and ccext2.dll is more consistent with the
posix libs, and it has clear advantages. I guess ccrtp will depend on
ccgnu2 only). I am going to modify Makefile.gcc and test. Should not
this change be made to the MSVC project files as well to keep
consistency?