remove boost as mandatory dependency #2409
Draft
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.
fix #481
Make boost an optional dependency.
alpaka::core::demangled<TYPE>
returns a mangled name in case boost is not available. #2405 can solve this but should not be mixed into this PR.This PR removes the mixing of alpakas own defines e.g
BOOST_LANG_HIP
which looked like boost but was exposed by alpaka under BOOST names.This PR is a base for discussion at the next developer meeting. In a separate PR we could reduce the number of tested boost versions. We should also run tests without boost at all.