Morten Eriksen writes:
> (So, in the Cygwin case it doesn't really matter whether you set the
> executable suffix to ".exe" or "", I guess.)
This equivalency only affects stat() and the PATH search of the shell. So
you can write makefiles like this:
fooprog: $(OBJS)
$(CC) -o $@ $^
install: fooprog
$(INSTALL) fooprog$(EXEEXT) $(bindir)
and they will work. But it probably doesn't in general on other systems
that have executable extensions. In fact, I'd have no idea how to act in
face of arbitrary $(EXEEXT) values.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
- Re: AC_PROG_CC not working Thomas E. Dickey
- Re: AC_PROG_CC not working Akim Demaille
- Re: AC_PROG_CC not working Bob Friesenhahn
- Re: AC_PROG_CC not working Akim Demaille
- Re: AC_PROG_CC not working Gary V. Vaughan
- Re: AC_PROG_CC not working Akim Demaille
- Re: AC_PROG_CC not working Gary V. Vaughan
- Re: AC_PROG_CC not working Peter Eisentraut
- Re: AC_PROG_CC not working Morten Eriksen
- Re: AC_PROG_CC not working Pavel Roskin
- Re: AC_PROG_CC not working Peter Eisentraut
- Re: AC_PROG_CC not working Pavel Roskin
- Re: AC_PROG_CC not working Morten Eriksen
- Re: AC_PROG_CC not working Earnie Boyd
- Re: AC_PROG_CC not working Earnie Boyd
- Re: AC_PROG_CC not working Pavel Roskin
- Re: AC_PROG_CC not working Earnie Boyd
- RE: AC_PROG_CC not working Bernard Dautrevaux
- RE: AC_PROG_CC not working Earnie Boyd
