[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_CHECK_PROGS and java compiler options
|
From: |
Ralf Wildenhues |
|
Subject: |
Re: AC_CHECK_PROGS and java compiler options |
|
Date: |
Sat, 22 Aug 2009 09:59:47 +0200 |
|
User-agent: |
Mutt/1.5.20 (2009-08-09) |
Hello John,
* John Calcote wrote on Fri, Aug 21, 2009 at 02:44:03AM CEST:
> I'm wondering about best practices for checking for programs like
> the javac compiler. For instance, I currently have a line in my
> project's configure.ac file that looks like this:
>
> AC_CHECK_PROGS([JAVAC], ["gcj -C -ftarget=1.4 -fsource=1.4" "guavac
> -target 1.4 -source 1.4" "jikes -target 1.4 -source 1.4" "javac
> -target 1.4 -source 1.4"])
Why are you doing this? AC_CHECK_PROGS will cut off the arguments when
searching for the program anyway, it don't try to run the program.
The semantics of AC_CHECK_PROGS are purely done so that one can pass in
variables to AC_CHECK_PROGS that are also used likewise elsewhere; but
for the tests done by this macro, they are not relevant.
Hope that helps.
Cheers,
Ralf