[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_PROG_CC not working
From: |
Akim Demaille |
Subject: |
Re: AC_PROG_CC not working |
Date: |
10 Oct 2000 13:58:33 +0200 |
User-agent: |
Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) |
>>>>> "Morten" == Morten Eriksen <address@hidden> writes:
Morten> The particular challenge I just bumped into is how to let
Morten> Autoconf configure know about a "self-made compiler", in the
Morten> sense that I have written a wrapper script around the MSVC++
Morten> cl.exe compiler (to let it behave properly when run from the
Morten> makefiles generated by Automake).
Why don't you
configure.in:
...
: ${CC-my_super_script_CC}
AC_PROG_CC
?
or
if under-ms; then
: ${CC-my_super_script_CC}
fi
AC_PROG_CC
Morten> 1) notify in the INSTALL file about needing to pass on
Morten> CC=[path/wrapperscript] when building with MSVC++. Simple
Morten> enough, but it doesn't seem like good policy to me to "push
Morten> complexity" on to the user.
Sooner or later, we will have such scripts. We already know we won't
be able to have all the compilers agree on the extension of Fortran
and C++ files.
Morten> 2) lobby to get my MSVC++ cl.exe wrapper script
Morten> shipped as a standard part of either the Autoconf or the
Morten> Automake distribution (and add the name of it to the list of
Morten> compilers AC_PROG_CC looks for).
Yes!
Akim
- AC_PROG_CC not working, Morten Eriksen, 2000/10/06
- Re: AC_PROG_CC not working, Akim Demaille, 2000/10/09
- Re: AC_PROG_CC not working, Pavel Roskin, 2000/10/10
- Re: AC_PROG_CC not working, Akim Demaille, 2000/10/10
- Re: AC_PROG_CC not working, Peter Eisentraut, 2000/10/10
- Re: AC_PROG_CC not working, Pavel Roskin, 2000/10/11
Re: AC_PROG_CC not working, Alexandre Oliva, 2000/10/10