Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: "Andre Oliveira da Costa" To: Subject: RE: [mingw32] Re: [RFC] changing gcc default output executable name (a.exe now) Date: Thu, 13 Jan 2000 16:44:44 -0200 Message-ID: <001901bf5df6$428a2170$8400000a@costa.cadenet.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal In-Reply-To: <46476C008A10D311BD0A0000C0775CF9DD6E72@srv-exchange.adtran.com> I'd like to ask for comments on another issue related to portability from UNIX --> cygwin, compilation etc.: the way it is now, the linker automagically appends a .exe suffix to the executable filename. If you do gcc -o foo foo.o ld will create foo.exe . I wouldn't complain about it except for the fact that this imposes a serious restriction to portability. For example, usually when I try to install a just-compiled application through "make install", all the cp, mv, chmod, strip and install rules refer to "foo" and not "foo.exe", and therefore they (rightfully) complain about missing files. So, even if the compilation goes out well, there's always some makefile tweaking involved. I don't think tweaking all these applications to look for "foo.exe" if they can't find "foo" would be the right thing. But I would really like to be able to install the applications I compile without having to tweak all the makefiles. Maybe the solution would be not to add the .exe suffix... Am I missing something or is this a real problem? Andre -- André Oliveira da Costa (costa AT cade DOT com DOT br) -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com