Make headerClassifier an optional field #185
Open
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
Member
|
headerClassifier should never be optional. Is there an actual use case for this? |
Member
Author
|
GradleRIO/native-utils doesn't care; if it doesn't have a header classifier it won't download headers. It would be reasonable to have a c++-only shared library that is only a link/runtime dependency. This also fixes #183 - REV doesn't publish headers for two of their driver libraries. |
ThadHouse
approved these changes
Nov 25, 2025
Member
I didn't realize the rest of the system was fine. Sounds good. |
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.
No description provided.