This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
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 09:37:42 +0530
- Subject: Cross-compilation and Shared Libraries
- Openpgp: url=http://ranjitmathew.hostingzero.com/aa_6C114B8F.txt
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I just noticed that even with "--disable-static --enable-static",
a Linux-to-MinGW cross compiler (mainline) still created static
libraries for the C++ and Java runtimes. Is this by design or is it
a bug? From the point of view of creating executables for embedded
platforms, this sort of makes sense but for a "full-fledged"
environment like MinGW, it doesn't - yes, it is a bit painful
to transfer the executable and all the libraries it depends on
to the target machine, but this should not be barred as such.
Or is there a more profound reason for this feature?
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
iD8DBQFEj4uOYb1hx2wRS48RApY/AJ9hXFfYyRRipZW2o29D0GFHd3bxcACfSL/s
8nBAEYP3FvoFFM1EjErEvPc=
=Z47d
-----END PGP SIGNATURE-----