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
Meson detects wrong framework for includes on macOS #3793
Comments
Kind of related to a part of #3402 |
ePirat
added a commit
to ePirat/meson
that referenced
this issue
Jun 26, 2018
The name splitting was wrong and would not incorrectly handle folders with two dots, like Foo.framework.dSYM and treat this as 'Foo' instead of 'Foo.framework', which would lead to meson detecting dSYM bundles as frameworks and try to use those like a framework, which is wrong. Fix mesonbuild#3793
jpakkane
pushed a commit
that referenced
this issue
Jun 26, 2018
The name splitting was wrong and would not incorrectly handle folders with two dots, like Foo.framework.dSYM and treat this as 'Foo' instead of 'Foo.framework', which would lead to meson detecting dSYM bundles as frameworks and try to use those like a framework, which is wrong. Fix #3793
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When detecting the Qt dependency, which are
.framework
s on macOS, Meson sometimes detects the wrong.framework
and uses that instead of the real one:As you can see, for the include it tries to use
/Applications/Qt/5.10.1/clang_64/lib/QtCore.framework.dSYM/Headers
in one case, which is the path to the dSYM bundle that contains debug information, not the Qt Core framework.The text was updated successfully, but these errors were encountered: