[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: split check target into check and test targets
From: |
Ralf Wildenhues |
Subject: |
Re: split check target into check and test targets |
Date: |
Tue, 2 Mar 2010 21:12:15 +0100 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
Hello,
* Steffen Dettmer wrote on Tue, Mar 02, 2010 at 11:00:39AM CET:
> On Wed, Feb 24, 2010 at 7:17 PM, John Calcote wrote:
> > Alexander's solution is great, though. I'm going to use that one myself.
>
> For this, you'd need to change all Makefile.ams and it isn't working
> recursively...
Yes.
> What is with having
>
> AC_SUBST(TESTS)
>
> in configure.in and running:
>
> $ make check TESTS=
>
> to skip test execution?
I don't see why you need the AC_SUBST in order to be able to do the
second line. In fact, it is typically harmful because when not used,
automake mangles the TESTS variable nicely for you, adding $(EXEEXT)
where needed and so on. You have to do that yourself in configure.
> > Additionally, if I want to build a particular check program (perhaps as I'm
> > working out the compiler errors, but before I'm ready to actually run the
> > tests), I just type "make <check-program-name>" from that directory.
>
> You just have to remember to add `.exe' on cygwin and MSYS,
> especially within scripts / make rules ($(EXEEXT)),
> otherwise (at least GNU-) make uses a default built-in rule
> to compile and link <check-program-name>, typically with
> different LIBS. The compiler command line looks plausible but
> fails and confuses people :-)
That, too.
Cheers,
Ralf