[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: best practice for injecting include dir across a project
From: |
Raja R Harinath |
Subject: |
Re: best practice for injecting include dir across a project |
Date: |
Fri, 25 Jul 2008 00:41:03 +0530 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
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"?
- Hari