[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Use of config.h: summary of responses.
From: |
Ralf Corsepius |
Subject: |
Re: Use of config.h: summary of responses. |
Date: |
Mon, 13 Sep 2004 18:00:51 +0200 |
On Mon, 2004-09-13 at 17:20, Bob Friesenhahn 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'.
Yes, but this is not what current autoconf's autoheaders are about.
> As for myself, I find that installing a trimmed-down configuration
> header which only includes the definitions required for the headers to
> work correctly is the best choice.
I have found myself in the same boat, but, and this might be a surprize
to you: Such config-headers in most cases boil down to very few defines,
which very easily can be encoded into very simple configure-script
fragments.
Ralf
- Use of config.h: summary of responses., Dale Mellor, 2004/09/13
- Re: Use of config.h: summary of responses., Ralf Corsepius, 2004/09/13
- Re: Use of config.h: summary of responses., Thomas Dickey, 2004/09/13
- Re: Use of config.h: summary of responses., Dale Mellor, 2004/09/13
- Re: Use of config.h: summary of responses., Thomas Dickey, 2004/09/13
- Re: Use of config.h: summary of responses., Daniel Reed, 2004/09/13
- Re: Use of config.h: summary of responses., Bob Friesenhahn, 2004/09/13
- Re: Use of config.h: summary of responses., Daniel Reed, 2004/09/13
- Re: Use of config.h: summary of responses., Bob Friesenhahn, 2004/09/13
- Re: Use of config.h: summary of responses., Daniel Reed, 2004/09/13
- Re: Use of config.h: summary of responses., Russ Allbery, 2004/09/13
- Re: Use of config.h: summary of responses., Andre Caldas, 2004/09/13
- Re: Use of config.h: summary of responses., Daniel Reed, 2004/09/14
Re: Use of config.h: summary of responses., Simon Josefsson, 2004/09/13