From: Mike Frysinger <vap...@chromium.org> The noinst_xxx targets will be compiled all the time. For test programs, the check_xxx targets make more sense as they'll only be built when the user runs `make check`.
* gettext-runtime/tests/Makefile.am (noinst_PROGRAMS): Rename to ... (check_PROGRAMS): ... this. --- gettext-runtime/tests/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gettext-runtime/tests/Makefile.am b/gettext-runtime/tests/Makefile.am index 4734012..0085994 100644 --- a/gettext-runtime/tests/Makefile.am +++ b/gettext-runtime/tests/Makefile.am @@ -26,7 +26,7 @@ AM_CPPFLAGS = \ -I.. \ -I$(srcdir)/../intl -noinst_PROGRAMS = test-lock +check_PROGRAMS = test-lock test_lock_SOURCES = test-lock.c ../intl/lock.c ../intl/threadlib.c test_lock_LDADD = @LIBMULTITHREAD@ @LIBSCHED@ -- 2.5.2
