Re: Non-recursive make with Fortran object files

On Wed, Dec 5, 2012 at 10:46 AM, Alexis Praga wrote: > Here is my answer. Sorry for not putting it into a separate mail. > > > >> Generating stuff only when "make install" is issued seems > counter-intuitive. > >> Why are you doing this exactly? >

Re: Non-recursive make with Fortran object files

stamp file, instead of creating a rule directly between the library and module files and the header ? -- Alexis Praga

Re: Non-recursive make with Fortran object files

there are created by my custom hook, I think automake remove them as there are seen as "created by automake". -- Alexis Praga

Non-recursive make with Fortran object files

question : I have scripts generated by make install (testing scripts). Can I tell automake not to delete them with "basic" clean, like mostlyclean ? There should be removed only if we really want to, not when cleaning .o files. -- Alexis Praga

Re: Several pass for a simple test in make check

Ha, yes. Simple and elegant. And we can use regexp for defining TESTS (not directly, but a temporary variable will work well enough). Adopted, thanks :) On Tue, Nov 20, 2012 at 5:06 PM, Stefano Lattarini < stefano.lattar...@gmail.com> wrote: > On 11/20/2012 03:58 PM, Alexis Pr

Re: Several pass for a simple test in make check

tests he wants to run. The only way to do that would be to generate again the list of test files and recreate a Makefile. Well, I suppose in general all the tests are run at once. But what if you have 200 tests, and only want to run the first 100 ? -- Alexis Praga

Re: Several pass for a simple test in make check

oing a 'ls' in the adequate directory. -- Alexis Praga

Re: TAP support documentation

utility (warning: will require perl); Thanks for the suggestion. Does it always come with perl ? For now, I would like to avoid too much dependencies. Maybe as a last resort measure. -- Alexis Praga

Several pass for a simple test in make check

Hi, Is it possible to have several "PASS" or "FAIL" output with a single script in TESTS ? I only have one script which loop over several configurations, so I would like to have one output for each iteration. 'make check' only write once in a log file for each test though. The TAP protocol allows

Re: TAP support documentation

TAP_LOG_DRIVER = env AM_TAP_AWK='$(AWK)' $(SHELL) \ >> $(top_srcdir)/build-aux/tap-**driver.sh >> TESTS = foo.test >> >> check: >>@for i in $(TESTS); do \ >> $(TAP_LOG_DRIVER) --test-name "$$i" \ >> --log-file $$i.log --trs-file $$i.trs -- $$i;\ >>

TAP support documentation

-name "$$i" \ --log-file $$i.log --trs-file $$i.trs -- $$i;\ done Do you think this hack can be used without too much surprise ? Otherwise, what do you recommand (upgrading is not an option) ? Thanks, Alexis Praga