This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 06/09/2010 08:08 AM, Andy Koppe wrote: >>> More importantly, a lot of build scripts likely depend on the .exe being added automatically. >> >> Hm. Maybe they shouldn't. > > Yeah, but "shouldn't" never stopped anyone, hence any transition would > certainly not be pain-free. A first step would be teaching gcc to not append .exe. Many configure scripts (certainly almost all scripts based on autoconf) determine $(EXEEXT) based on gcc behavior, and will just do the right thing throughout the rest of the build with $(EXEEXT) empty (as evidenced by their behavior on Linux). But even with that gcc change, we'd have to keep .exe magic in cygwin1.dll until everything in the distro has been rebuilt without an .exe suffix. However, I'm starting to like the idea, if we can get buy-in from the gcc packager. Dave? Meanwhile, the (as-yet-pending) cross-compiler to build mingw executables _should_ continue to output .exe suffix, and anything trying to still be portable to mingw will have to be even more careful to use $(EXEEXT) properly because cygwin would no longer be helping out (but then again, that's exactly the situation you face when using wine, since Linux is not helping out). -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |