Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 13 Jan 2000 15:08:19 -0500
To: Andre Oliveira da Costa <costa AT cade DOT com DOT br>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: [mingw32] Re: [RFC] changing gcc default output executable na me         (a.exe now)
Message-ID: <20000113150819.A7494@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: Andre Oliveira da Costa <costa AT cade DOT com DOT br>,
	cygwin AT sourceware DOT cygnus DOT com
References: <C9A8E1D07093D111B76A0000F8C9918A026E1656 AT zrtpd003 DOT us DOT nortel DOT com> <002a01bf5dfc$97121670$8400000a AT costa DOT cadenet DOT com DOT br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <002a01bf5dfc$97121670$8400000a@costa.cadenet.com.br>; from costa@cade.com.br on Thu, Jan 13, 2000 at 05:30:03PM -0200

On Thu, Jan 13, 2000 at 05:30:03PM -0200, Andre Oliveira da Costa wrote:
>Mmmh... ok, I agree this would solve the problem for packages which use
>autoconf/automake. But those who don't are still in the dark. The worst of
>it all is that the .exe suffix is added by ld -- it is as if cygwin creates
>problems for itself...
>
>(before flaming starts: I know there's a very good reason for the insertion
>of the .exe suffix: it has to be added so that the files can be seen as
>executables by Windoze -- another great feature (?) by M$oft... =T As I
>said, I just think it would be nice to have this .exe suffix handled
>transparently, since it is automagically created)

As usual, my suggestion is that rather than opine how something should be
handled "automatically", actual source code demonstrating your idea would
be much more helpful.

The sources to cp, cygwin, mv, rm, make, gcc, etc.  are all available.
Personally, I have no idea how you could implement a plan to
"automatically" do the right thing in such a way that you will end up
satisfying everybody.  However, I'd love to be proved wrong by seeing
exactly what you are proposing.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com