[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make install : config.h?

From: Guido Draheim
Subject: Re: make install : config.h?
Date: Fri, 26 Jul 2013 12:00:02 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7

Am 25.07.2013 00:05, schrieb Peter Johansson:
On 07/24/2013 07:39 PM, LRN wrote:
Or even better, separate config.h into two files - use one internally
(normal config.h), while the other will be both installed and used
internally (sadly, i can't tell you how exactly that can be done; is generated by autoheader, so they will have to either
tinker with autoheader, or just form the second (smaller) header
manually, at least an .in template of it).
We do exactly this in yat. We create a 'yat/utility/config_public.h' from 
'yat/utility/', which is then installed. For details please 


However your file does contain definitions without a prefix

#undef HAVE_BAM_H

So when a third project includes your config_public.h and a local
config.h .. then you would kill any "#define" of the local config.h
thereby creating some irrititating behaviour where the
sad "bam.h found" and the #ifdef'ed section is skipped.

I'd advise strongly against installing a public header with definitions
as they are produced for a local config.h - do always use a prefix. (You
have done that for the other names in the public_config.h)

To avoid creating a manually, I let it be generated
automatically from the config.h by an additional autoconf macro:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]