[C/C++] CMake: Resolve package configuration install destination mismatch #1536
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
martin4861
approved these changes
Nov 14, 2025
Contributor
martin4861
left a comment
martin4861
left a comment
There was a problem hiding this comment.
lgtm, thanks for the fix!
ethanmusser
deleted the
ethanmusser/bug/1533-pkg-config-install-destination-mismatch
branch
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.
Description
@swift-nav/algint-team
Fix a mismatch between the configured package configuration file's install destination and the actual install destination.
Resolves #1533.
API compatibility
Does this change introduce a API compatibility risk?
No, the source code is not changed. Only consumers building and then relocating their package configurations should be affected, and it should simplify the process without breaking existing workflows.
API compatibility plan
If the above is "Yes", please detail the compatibility (or migration) plan:
N/A
JIRA Reference
N/A