Resolves bug #15560 - evaluate qt dependencies without qt framework#15623
Resolves bug #15560 - evaluate qt dependencies without qt framework#15623boulette42 wants to merge 1 commit into
Conversation
|
Please update the commit message to use a standard format. e.g. following the guidance at https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html In particular, "resolves #15560" should be part of "more detailed explanatory text" because it is a citation that explains "detect non-framework Qt on macOS" -- the bug reference isn't the actual one-line summary itself. Also, "resolves #xxx" is a keyword recognized by GitHub to automatically close linked tickets, but "resolves bug #xxx" is unfortunately not part of the GitHub regex, so please never use the latter. |
If qt5 was built from source with parameter '-no-framework', meson did not find the Qt-libraries. Now instead of changing an internal flag, the return code of the probing function is used to determine the existence of the qt framework. The internal flag has to keep its value. This resolves mesonbuild#15560
|
Thank you for your advice. |
|
Who sets |
bonzini
added
the
needs-info
|
@boulette42 can you answer the question above? |
3 participants
If qt5 is built from source with parameter '-no-framework', meson did not find the Qt-libraries. Instead of changing an internal flag, the return code of the probing function is now used to determine the existence of the qt framework. The internal flag has to keep its value.
Fixes: #15560