This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
DLLs for GCC/Windows (Was: Re: Cross-compilation and Shared Libraries)
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: gcc at gcc dot gnu dot org
- Date: Wed, 14 Jun 2006 22:53:49 +0530
- Subject: DLLs for GCC/Windows (Was: Re: Cross-compilation and Shared Libraries)
- Openpgp: url=http://ranjitmathew.hostingzero.com/aa_6C114B8F.txt
- References: <e6o21q$e63$1@sea.gmane.org> <448F9452.E16F5938@dessent.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brian Dessent wrote:
>
> As far as I know, shared libstdc++ for mingw/cygwin has never worked,
> you always get static no matter what you do, regardless of
> --enable-shared or native/cross. I don't know if this is because of the
> archaic version of libtool that's in the tree, or some other reason. It
> sure would be nice to get a shared libstdc++ one of these days without
> having to resort to hacks like manually linking together all the .o
> files in the build tree.
The libtool in the GCC tree seems to need --enable-win32-dll
to build DLLs for Windows runtimes, which it would use only
if the library defines AC_PROVIDE_AC_LIBTOOL_WIN32_DLL - I
defined:
AC_DEFUN([AC_PROVIDE_AC_LIBTOOL_WIN32_DLL],[])
in libstdc++-v3's configure.ac and regenerated configure.
libtool also wants ld_shlibs to be set to "yes" and this
I achieved by putting "ld_shlibs=yes" under the case label
for "mingw*" in ltcf-cxx.sh.
With these kludges, GCC tries to build libstdc++ as a DLL,
but fails with undefined references to a whole bunch of
stuff (crossed-native build on Linux).
I'll investigate this issue later.
Thanks,
Ranjit.
- --
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://rmathew.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEkEYkYb1hx2wRS48RApEfAJ9yCJPA5Pjk9+FjFQ8Y1nU27l6nHgCfZeKV
YX+VfsdJE6ipkZvj8wgew8U=
=XrJZ
-----END PGP SIGNATURE-----