Allow config #defines to be written out to custom config/defines.hpp … #2398
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The existing cmake macro can be used to generate #defines for the global
hpx/config/defines.hpp file by using
and then written to hpx/config/defines.hpp using a new macro and
specifying the default namespace
This keeps the existing behaviour unchanged.
However a new NAMESPACE feature is supported to allow the user to add
and then to generate a defines.hpp file as follows
when no template is specified, the function will generate a copyright
block, and include guard #ifndef...#endif section with the #defines between.
In the above example, the following would be generated from the variables
This feature allows a module (e.g. parcelport) to generate #defines without
writing to the global defines.hpp file and triggering full rebuilds on every change.