Mail Archives: cygwin/2003/10/12/01:35:24
--=-biJHE1Pw9Ed5HrkLwVuq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
For crying out loud.
Edward, there are plenty of archives and resources that detail how to
achieve your stated goals. Right now you are making suggestions from a
quite apparent position of ignorance. I urge you to research before you
suggest fixing something that isn't broken. All the cygwin packages come
with source that will build. The GPL issues are clearly documented on
the FSF website - there is a FAQ on the GPL and how it applies to
binaries and source. And so forth.
cygwin1.dll, the portability layer/platform can be cross compiled to
from mingw, from linux, from BSD etc etc etc.
mingw aka the MSVCRT runtime can be cross compiled to from cygwin, from
linux, from BSD etc etc etc.
and both support native compilation (cygwin-> cygwin, mingw->mingw).
As for needing two dev environments, you been instructed how to use
cygwin to compile to both, so I must conclude you are not actually
trying to comprehend the emails, just arguing for the sake of it.
Rob
--=20
GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.
--=-biJHE1Pw9Ed5HrkLwVuq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/iOgGI5+kQ8LJcoIRAvYxAJ9xemgCa4qQj0ujsyTNn8xT9D5IgACbB55x
aEqO570EcFqQ402PRn6YH/8=
=qT7b
-----END PGP SIGNATURE-----
--=-biJHE1Pw9Ed5HrkLwVuq--
- Raw text -