Hi Ralph,
On 2017-11-20, Ralph Corderoy wrote:
>> It seems wrong for foo.y to have to `#include
>> "path/from/root/to/bar.h" since that means it has to alter if they
>> move around the hierarchy. Is there another way?
>
> I can be more precise having dug into this project a bit.
> Currently, it
More noise...
> It works in this one case, but I know that doesn't necessarily mean
> it's right. :-)
I've found AM_CPPFLAGS in `info automake | less' and I think that's
answering it.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi again,
> It seems wrong for foo.y to have to `#include
> "path/from/root/to/bar.h" since that means it has to alter if they
> move around the hierarchy. Is there another way?
I can be more precise having dug into this project a bit.
Currently, it has
sbr_libmh_a_CPPFLAGS = ${AM_CPPFLAGS}
Hi,
In a subdirectory, a foo.y gets turned into a foo.c. Both thus
`#include "bar.h"' that sits alongside them. This all works fine. But
use a build directory, i.e. run configure from somewhere other than `.',
and foo.c fails to build because bar.h isn't found. (A similar problem
happens with
