[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Patches to compile CC++ 2 for Win32 with GCC using Mingw32
From: |
David Sugar |
Subject: |
Re: Patches to compile CC++ 2 for Win32 with GCC using Mingw32 |
Date: |
Fri, 9 Aug 2002 13:33:40 -0400 |
User-agent: |
KMail/1.4.1 |
It appears I went thru the same things with libxml2 and iconv on my debian
mingw32 toolchain that you had already hit :). Yes, I cannot get dll builds
out of those things under the debian tool chain either at the moment. I
recall the latest cygwin with patched autoconf/automake and updated binutils
can now successfully produce dll's, while the debian autoconf, automake, and
mingw32 gcc/binutils probably predate this by a lot.
You might want to look at my modified Makefile.gcc in cvs. I did a few small
changes and also added the build targets for the demo and test apps. I think
splitting the dll's into two like the posix targets makes the most sense,
especially with libxml2 statically linked; the single dll image is big :).
On Friday 09 August 2002 13:11, Federico Montesino Pouzols wrote:
> > 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?