Use the new target names for ACTS #470
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It looks like |
|
Thanks, @tmadlener. Yes, the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Acts has switched to namespaced targets in v42. This little change makes things work again for newer versions.
@kjvbrt do we want to have backwards compatibility? That would be relatively straight forward to add, see e.g.: key4hep/k4ActsTracking#26
I would like to have this in, because then I would also be able to add this to a newly created Acts CI workflow that tests Key4hep dependencies, so that we can get a ping earlier if things break: acts-project/acts#4663