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 lex's C output.)

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?

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

Reply via email to