We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi there. I'm the maintainer of the bctoolbox port over at MacPorts.
It looks like the Frameworks installation location is hard-coded in the following lines:
bctoolbox/src/CMakeLists.txt
Lines 286 to 305 in 388770f
... on the line:
FRAMEWORK DESTINATION Frameworks
MacPorts uses the following directory for frameworks: ${prefix}/Library/Frameworks. For example: /opt/local/Library/Frameworks/Python.framework.
${prefix}/Library/Frameworks
/opt/local/Library/Frameworks/Python.framework.
I tried to fix this with my patch, but I'm not sure if it does not break anything.
https://raw.githubusercontent.com/macports/macports-ports/master/devel/bctoolbox/files/patch-fix-Frameworks-path.diff
Could you please provide a separate option in CMake that could be used to define a path to install frameworks?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi there. I'm the maintainer of the bctoolbox port over at MacPorts.
It looks like the Frameworks installation location is hard-coded in the following lines:
bctoolbox/src/CMakeLists.txt
Lines 286 to 305 in 388770f
... on the line:
MacPorts uses the following directory for frameworks:
${prefix}/Library/Frameworks
. For example:/opt/local/Library/Frameworks/Python.framework.
I tried to fix this with my patch, but I'm not sure if it does not break anything.
https://raw.githubusercontent.com/macports/macports-ports/master/devel/bctoolbox/files/patch-fix-Frameworks-path.diff
Could you please provide a separate option in CMake that could be used to define a path to install frameworks?
The text was updated successfully, but these errors were encountered: