-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eric Blake wrote:
> No. With Corinna's patch to add CYGWIN=transparent_exe option, we are
> asking for problems if we distribute a script alongside an exe. (I've
> been meaning to check for any other violations of the idea of providing
> more than one file in the set {foo, foo.exe, foo.lnk, foo.exe.lnk}, since
> I would like to see transparent_exe gain more light).
OK, but I can think of one *major* "violation" of this: libtool-built
applications, when linking against a to-be-installed library in the same
package. In such a case, the real .exe is placed in .libs, and both an
extension-less libtool script and a launcher .exe are placed in the
builddir; this allows one to run the application w/o installing it.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEB2xtpiWmPGlmQSMRAl4KAJ9etjDQmJLxykewiZPybDT5itx6oACg9Dgr
7JMp86OzTcvKk+9JVYDV1kc=
=nj/K
-----END PGP SIGNATURE-----
