I'm afraid people do not pay attention to output. if build doesn't fail, why should they ?
I can add that message, even make it any colour. 2016-06-23 16:32 GMT+05:00 Gert Doering <g...@greenie.muc.de>: > Hi, > > On Wed, Jun 22, 2016 at 10:41:48PM +0200, Steffan Karger wrote: > > > -test_scripts = t_client.sh t_lpback.sh t_cltsrv.sh > > > +test_scripts = t_client.sh > > > +if ENABLE_CRYPTO > > > +test_scripts += t_lpback.sh t_cltsrv.sh > > > +endif > > > > > > TESTS_ENVIRONMENT = top_srcdir="$(top_srcdir)" > > > TESTS = $(test_scripts) > > > > Ah, this is even cleaner than AC_SUBST. But this matches what I had > > in mind, yes. (I didn't test, but I assume this simply doesn't run > > these tests?) > > make will not even know that these tests exist, so "doesn't run these > tests", yes :-) > > I *am* wondering if there is a clever way to print out "not running self > tests due to lack of --disable-crypto", so people are made aware that > this is less well tested... > > gert > > -- > USENET is *not* the non-clickable part of WWW! > // > www.muc.de/~gert/ > Gert Doering - Munich, Germany > g...@greenie.muc.de > fax: +49-89-35655025 > g...@net.informatik.tu-muenchen.de >
