|
From: | Bob Friesenhahn |
Subject: | Re: #define warnings when using various autotools projects |
Date: | Tue, 13 May 2008 14:16:34 -0500 (CDT) |
On Tue, 13 May 2008, John Calcote wrote:
For my own project, I use two "config.h" files. One is used to build the software and the other is trimmed down to support only what is actually needed to define the interface header ABI.And what if a user decided to run "make install" to put your public headers into his or her /usr/local/include directory? Or even worse--what if a distro packager decides to provide a "devel" package for your project that installs your public headers into "/usr/include"? How is it that you're okay claiming ownership of the one "config.h" header that is allowed to exist in this directory?
Quite simple. I use a namespace-scoped name for the publically installed "config.h". I also use namespace-scoped defines in the publically installed "config.h". This is much simpler than the various complex substitution schemes I have seen described on this list and elsewhere.
Bob ====================================== Bob Friesenhahn address@hidden, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
[Prev in Thread] | Current Thread | [Next in Thread] |