Re: Use of config.h: summary of responses.

[Andreas Schwab]

Stepan Kasal <address@hidden> writes:

> 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.

In case of bfd-in2.h it's generated be AC_CONFIG_FILES.  It only depends
on the format of the substitution, either @FOO@ or #define FOO.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."