On Sat, 20 Jan 2007, David Byron wrote:
"config.h" may be provided from multiple packages at once
and all included instances may be required. The user that
includes it needs to manage proper use.
Any suggestions how? I've seen people write scripts to modify/rename
config.h but that seems overkill in this case.
The simple solution is to have one of your own headers make the
necessary inclusions and prevent any accidental multiple-inclusion.
If there are multiple header files named config.h, then some
additional means must be used to discriminate between them, such as
including their parent directory path.
Bob
======================================
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
