#631 Document the ENABLE_FOO buildsystem trick
Metadata
| Property | Value |
|---|---|
| Reported by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Reported at | Oct 30, 2009 11:44 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
| Last edited at | Apr 24, 2012 20:44 |
| Closed by | Christoph Grüninger (gruenich@iws.uni-stuttgart.de) |
| Closed at | Apr 24, 2012 20:44 |
| Closed in version | Unknown |
| Resolution | Implemented |
| Comment |
Description
Various m4 tests for external libraries (e.g., Alu or UG) do not simply set
#define HAVE_FOO 1
in config.h. Instead, the line is
#define HAVE_FOO ENABLE_FOO
The flag ENABLE_FOO is then set by a -D options added automagically to the FOO_CPPFLAGS.
The purpose of this twist may not be intuitively clear to our younger readers. We should therefore document it, preferably in prose in the buildsystem tutorial.