-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
cmake: do not force building with the install name dir #65656
cmake: do not force building with the install name dir #65656
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should have documentation for this flag. You can defer that until we've hashed out the behaviour and the flag itself though. 🙂
771dc03
to
d498410
Compare
Well, I have no idea what CI is choking on… |
Try rebasing. Seems there may have been some CI breakages in master. |
d498410
to
6cb4198
Compare
@tambry Thanks for the review. FYI, I do not have merge rights, so someone else will need to hit the button for me. |
Could you update the commit message to reflect that it's no longer undocumented?
|
When custom install names and rpaths setups are used they may not work in the build tree as-is (namely when using absolute paths for install names in order to avoid rpath juggling in downstream projects). Add a flag for opting out of this behaviour. See: https://reviews.llvm.org/D42463
Thanks. Updated. |
6cb4198
to
a52e378
Compare
When custom install names and rpaths setups are being used, they may not work in the build tree as-is (namely when using absolute paths for install names in order to avoid rpath juggling in downstream projects).
Use an undocumented flag to control this as it is fairly advanced.
See: https://reviews.llvm.org/D42463
I can add docs and a cache entry for this if wanted.