On Thu, Jul 31, 2014 at 9:32 PM, David Beer wrote:
> Gavin,
>
> Thanks for your reply. Here's a more specific breakdown of what the project
> does:
>
> src/a/Makefile.am:
>
> a_SOURCES = bob.c tom.c
>
> src/b/Makefile.am:
>
> b_SOURCES = mary.c ../a/tom.c
>
> The purpose was so that tom.c would be
Gavin,
Thanks for your reply. Here's a more specific breakdown of what the project
does:
src/a/Makefile.am:
a_SOURCES = bob.c tom.c
src/b/Makefile.am:
b_SOURCES = mary.c ../a/tom.c
The purpose was so that tom.c would be recompiled with a different
preprocessor switch. There were only a few fi
On Thu, Jul 24, 2014 at 4:48 PM, Steffen Dettmer
wrote:
> Hi,
>
> I have a test that generates a log file, which I can manually run via
> "make check". Is there a simple way to automate that? For the moment I
> just created a pragmatic target "autotest", but I think it is ugly
> (and too specific
On Thu, Jul 24, 2014 at 4:48 PM, Steffen Dettmer
wrote:
> Hi,
>
> I have a test that generates a log file, which I can manually run via
> "make check". Is there a simple way to automate that? For the moment I
> just created a pragmatic target "autotest", but I think it is ugly
> (and too specific)
On Thu, Jul 24, 2014 at 9:09 PM, David Beer wrote:
> All,
>
> I am currently trying to get our project completely compatible with
> automake 1.14. We have multiple places where we compile a source file from
> another of the project's subdirectories in a given subdirectory. The two
> main use cases
