15.2.3 Parallel Test Harness
The example given in this section:
TESTS = foo.pl bar.py baz
TEST_EXTENSIONS = .pl .py
PL_LOG_COMPILER = $(PERL)
AM_PL_LOG_FLAGS = -w
PY_LOG_COMPILER = $(PYTHON)
AM_PY_LOG_FLAGS = -v
LOG_COMPILER = ./wrapper-script
AM_LOG_FLAGS = -d
Shows specific identification of compilers, sic. PL_LOG_COMPILER and
PY_LOG_COMPILER. Automake seems to have knowledge of particular language
compilers and the user can specify their use as in:
check_JAVA
check_LISP
check_PYTHON
For _JAVA, _LISP, _PYTHON can I use check_ or must I separately specify a
compiler as in ext_LOG_COMPILER and not use check_?
And just as a nit-noy, the document is clear to say that an AM_ prefix means
that the variable is available to the developer and if AM_ is missing then
the variable is available to the user. Why aren't ext_LOG_COMPILER prefixed
with AM_ext_LOG_COMPILER as is done with AM_ext_LOG_FLAGS?
Maintenance turns design into chaos
