[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Use of config.h: summary of responses.
From: |
Stepan Kasal |
Subject: |
Re: Use of config.h: summary of responses. |
Date: |
Fri, 7 Jan 2005 10:57:12 +0100 |
User-agent: |
Mutt/1.4.1i |
Hi,
4 months ago, Bob Friesenhahn <address@hidden> wrote:
> > The fact of the matter is that some/many libraries have header files
> > which are OS/CPU/compiler dependent and there has to be a way to
> > record/work-around these dependencies so that the library headers work
> > right. This way is commonly known as 'config.h'.
Resurrecting that ancient thread, Ian Lance Taylor writes:
> Then we substitute in bfd-in2.h as we do in config.h, by adding it to
> AC_CONFIG_FILES. Then we install the result.
you mean AC_CONFIG_HEADERS, of course.
Stepan