Example: Build and run also with static linking #498
Merged
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.
Statically linking requires that transitional dependencies are correctly described by the CMake targets.
Link executables in the example that are statically linked to the SuiteSparse libraries, and run them in the CI to check that.
That's not an extensive test. (Theoretically, we'd need to check if linking any combination of libraries works correctly.) But it's better than nothing.
This also revealed an issue when trying to link to a static library that was built with nvcc:
I think the relevant change was setting CUDA_RESOLVE_DEVICE_SYMBOLS to
ON
.