> -----Original Message-----
> From: edward [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 11:27 AM
> To: Robert Collins; Akim Demaille
> Cc: [EMAIL PROTECTED]
> Subject: Re: program target missing $(EXEEXT)
>
>
> yep. enclosed is a patch which demonstrates how i deal with that. the
> *first* set of unidiff marked is the part that came up as
> unacceptable.
> unfortunately, the rest really don't work w/o it. the 2nd
> unidiff marked is
> something i'm trying to track down. that is, how to deal properly with
> SUFFIXES = and extension map. so please ignore. the rest is really the
> "meat" of how i'm currently (brokenly in terms of philosophy,
> but it *does*
> work) handling exe. this patch is mostly meant as a
> conceptual demonstration
> more than anything else.
>
> generally, i only re-write the rules that require it. for
> example, gcc on
> wintel is .exe aware. unfortunately, rm isn't. so clean
> targets need to be
> updated. it's pretty important to keep the bin targets free
> of .exe however,
> if you want to use libtool for creating dlls and apps that use dlls.
I still have a philosophical issue here. You're handling "known
programs". I really think the right way to do this is handle "known
platforms". Compilers on cygwin/mingw/os2/dos that need .exe are the
rule not the exception. To pick an example, rm, if the user is on mingw,
that won't be rm, it'll be "$(SHELL) delete". What then?
Rob
> cheers.
>
> --- automake.in.~1.995~ Mon Mar 26 21:31:18 2001
<skip>
