On Thu, 8 Mar 2007, Daniel Richard G. wrote:
> Problems with this:
>
> 1. If the user runs ./configure, the file gets blown away
Yes, but the user shouldn't care. A ./configure user ideally shouldn't
have received config.h in the first place.
> 2. It confuses the issue for out-of-source-tree builds (do we use
> $(srcdir)/config.h, or $(builddir)/config.h?)
Good point.
> 3. It's poor form to distribute what is technically a system-specific file
Indeed.
> 4. There is precedent for distributing hand-tuned config.h files under
> suffixed names (e.g. config.h.win32, config.h.vms)
Also true.
I think on balance that config.h.generic and pcre.h.generic are perhaps
what I should go for.
Philip
--
Philip Hazel, University of Cambridge Computing Service.
