Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix LSTCore compatibility #22

Closed
wants to merge 1 commit into from

Conversation

ariostas
Copy link
Member

@ariostas ariostas commented May 1, 2024

This is a companion PR to SegmentLinking/TrackLooper#395. In that other PR I made some changes so that the master branch is compatible with LSTCore. However, since the LST package uses some of the headers, we need to set LST_STANDALONE when using it as an external so that headers are included properly.

@@ -3,6 +3,7 @@
<use name="lst_headers"/>
<use name="DataFormats/TrackerRecHit2D"/>
<use name="HeterogeneousCore/AlpakaInterface"/>
<flags CXXFLAGS="-DLST_STANDALONE"/>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

now that it's explicitly here, I'm thinking if LST_EXTERNAL is a more appropriate name to avoid confusion in the purpose.
Since either EXTERNAL or STANDALONE are technically to indicate a negative of being in CMSSW, perhaps even better is to use smth like LST_IS_CMSSW_PACKAGE

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think something like LST_IS_CMSSW_PACKAGE makes sense. I'll close this PR and make the required changes to the other PR.

@ariostas ariostas closed this May 1, 2024
@ariostas ariostas deleted the LSTCore_compatibility branch May 28, 2024 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants