Philippe Proulx writes:
> On Tue, Aug 8, 2017 at 5:06 PM, Mathieu Lirzin wrote:
>
>>
>> --8<---cut here---start->8---
>> foo_tests = foo/...
>> bar_tests = bar/...
>>
>> TESTS = $(foo_tests) $(bar_tests)
>>
>> check-foo:
>> $(MAKE) $(AM_MAKEFLAGS) TEST
On Tue, Aug 8, 2017 at 5:06 PM, Mathieu Lirzin wrote:
>
> Hello,
>
> Philippe Proulx writes:
>
> > So I put a TESTS variable in a/Makefile.am, b/Makefile.am, and
> > c/Makefile.am, and remove the TESTS variable from tests/Makefile.am. Now
> > I can go to a/, b/, or c/ and run `make check` to test
Hello,
Philippe Proulx writes:
> So I put a TESTS variable in a/Makefile.am, b/Makefile.am, and
> c/Makefile.am, and remove the TESTS variable from tests/Makefile.am. Now
> I can go to a/, b/, or c/ and run `make check` to test only specific
> parts of the project. However, since each individual
My project has the following directory structure (some files hidden for
clarity):
Makefile.am
tests/
Makefile.am
a/
Makefile.am
b/
Makefile.am
c/
Makefile.am
If I put all the tests to run that are in the a/, b/, and c/
subdirectories in the
On Aug 7, 2017, at 11:39 PM, Dharmil Shah wrote:
>
> I followed your suggestions and hence I am able to compile my package using
> the llvm compiler.
I hope you chose option 3.
On re-reading that email, I think option 2 is wrong, or at least, it isn’t what
I meant to write:
$ ./configure
