You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuration headers (config.h, etc.), as their name implies, are
supposed to contain macro definitions to avoid having them to pass
on the command line[1]. It seems fine if they include other
configuration headers when needed. In any way, they are supposed to be
included very early in compilation units which require them.
Doing more than defining simple macros, possibly guarded by defines set
during compile time (such as a compiler or platform identification),
can lead to subtle issues, which may go unnoticed such as the fallback
definitions in the hard-coded (!) fpm_config.h, which may actually be
used unconditionally, because the appropriate system headers have not
already been included.
[1] <https://www.gnu.org/software/autoconf/manual/autoconf-2.72/html_node/Configuration-Headers.html>
0 commit comments