[ccan] config.h
Rusty Russell
rusty at rustcorp.com.au
Sun May 31 12:42:24 AEST 2015
"Emilio G. Cota" <cota at braap.org> writes:
> On Fri, May 29, 2015 at 16:15:43 +0200, Delio Brignoli wrote:
>> Is there a reason for the CCAN configuration header being named
>> config.h instead of (for instance) ccan_config.h?
>> Would it be acceptable to add a namespace prefix like ‘ccan_’
>> to it to avoid clashes?
>
> Renaming config.h is not the only problem to fix wrt potential
> namespace clashes. See this thread for more info:
>
> https://lists.ozlabs.org/pipermail/ccan/2014-March/000622.html
Hi Emilio,
Thanks for the reminder.
There's nothing "ccan-specific" about config.h, and I think it's a bad
idea to make it so. Almost every project wants one, and autconf
etc. can certainly generate one to keep ccan happy.
Hmm, perhaps I should write that, since it seems to be an FAQ?
Thanks,
Rusty.
PS. Yeah, I still need to get rid of the ccan makefiles by providing
a decent replacement...
More information about the ccan
mailing list