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

Remove INSTALL_NAME_DIR target property #59

Conversation

fbudin69500
Copy link

Using INSTALL_NAME_DIR target property forces the install name to be an
absolute path instead of @rpath/{target_name} [1]. This causes problems
when one tries to relocate the target once it is installed.
This patch removes this target property. If a project needs to keep
the absolute path, CMake variables such as INSTALL_NAME_DIR can be set at
configuration to do so.

[1] https://gitlab.kitware.com/cmake/cmake/issues/16589

Using INSTALL_NAME_DIR target property forces the install name to be an
absolute path instead of `@rpath/{target_name}` [1]. This causes problems
when one tries to relocate the target once it is installed.
This patch removes this target property. If a project needs to keep
the absolute path, CMake variables such as INSTALL_NAME_DIR can be set at
configuration to do so.

[1] https://gitlab.kitware.com/cmake/cmake/issues/16589
@fbudin69500
Copy link
Author

@jcfr Not sure if you had time to review this PR. Just a ping.

jcfr added a commit that referenced this pull request Sep 21, 2017
@jcfr
Copy link
Member

jcfr commented Sep 21, 2017

Integrated in fa7c647

Note: This change doesn't impact CTK or Slicer since PythonQt is not explicitly installed on MacOSX

@jcfr jcfr closed this Sep 21, 2017
jcfr added a commit that referenced this pull request Sep 21, 2017
@jcfr
Copy link
Member

jcfr commented Sep 21, 2017

Backported to patched-6 branch as b85ef8a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants