feat: set CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS=ON#248
Open
feat: set CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS=ON#248
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Sets a container-wide default so CMake’s find_package() resolves symlinked paths to their real locations, improving behavior when developing against the in-container filesystem layout.
Changes:
- Adds
CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKS=ONto the final image environment. - Documents the intent directly in the Dockerfile near the view/symlink handling.
wdconinc
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Briefly, what does this PR introduce? Please link to any relevant presentations or discussions.
This PR sets the environment variable
CMAKE_FIND_PACKAGE_RESOLVE_SYMLINKSto resolve symlinks in CMake.What is the urgency of this PR?
What kind of change does this PR introduce?
Please check if any of the following apply
Instead of a single de-duplicated
-I/opt/local/includeyou will likely end up with many long paths in compilation commands.