Re: best practice for injecting include dir across a project

[Monty Taylor]

Raja R Harinath wrote:
> Hi,
> 
> Monty Taylor <address@hidden> writes:
> 
>> I've got a project that has 24 Makefile.am files. At the top of all of
>> them at the moment, I've got:
>>
>> AM_CPPFLAGS = -I$(top_builddir)/include -I$(top_srcdir)/include
> [snip]
>> PS. Yes...I know the -I$(top_builddir)/include is ridiculous... I
>> inherited that and just haven't gotten rid of it yet... but the
>> fundamental question of "how do I add one or more include paths globally
>> from a top level in a sane manner still holds...
> 
> Since your main question got answered...  What's wrong with
> -I$(top_builddir)/include?  It's most definitely not redundant.  Of
> course it can be superfluous if you don't have any generated header
> files in the build tree.  But, why "ridiculous"?

Well... "ridiculous" may have been a bit strong... we generate a couple
of header files, and each of them could be done in a better way. So I'm
probably just projecting my hatred of my generated headers... :)

Monty