[Ccrtp-devel] Re: Patches to compile CC++ 2 for Win32 with GCC using Mingw32

[David Sugar]

I think we should probably have an updated ccrtp release out soon...

Yes, a lot of people have been reworking libtool for cygwin and perhaps 
ignoring mingw32 in the process...I happen to prefer mingw32 (cross compiled) 
rather than the nativily hosted cygwin32 because I can build those target 
binaries on a free system.  That being said, I think it is also useful and 
helpful to have standard free software applications and open protocol 
implementations available on all platforms.  In the end this will be 
important for things like a gnu softphone project.

Out of curiosity, and somewhat related, can the debian hosted mingw32 binutils 
link things in omf format (like "xxx.lib") files as well as the coff/elf 
objects it already supports?  And can one generate omf ".lib" files out of 
.a's, such as from the libccgnu2.a dll stub?

David

On Friday 09 August 2002 13:48, you wrote:
> > I was thinking of creating a "win32" directory and a "Makefile.gcc" for
> > ccscript and ccuadio to do dll builds thru mingw32 with the hand-coded
> > makefiles anyway.  Maybe we could do this for ccrtp at least for now
> > until  the toolchain/autoconf/automake stuff catches up for cross
> > compiled  win32 dll's.
>
>    Yes, I had already done a makefile for ccrtp and mingw. For ccrtp I
> currently have a win32 directory that contains two directories: msvcpp and
> mingw32. The first has the workspace/project files of VC++; the second
> has a GNUccRTP.mak makefile for mingw32 generated through the script
> dsw2mak.awk.
>
>    As for the autotools, the latest versions I have tried are:
>
>    autoconf 2.53
>    automake 1.6.2
>    libtool 1.4.2a
>
>    I suspect that libtool is the "culprit", looking at its code, it seems
> very oriented towards cygwin dlls.
>
> > David
> >
> > On Fri, 9 Aug 2002, 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?
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Bug-commoncpp mailing list
> >> address@hidden
> >> http://mail.gnu.org/mailman/listinfo/bug-commoncpp