Musescore compile on MacOS 10.14 (Qt version 5.12.2)
I am trying to compile musescore on MacOS but it is throwing me an error:
CMake Warning at build/FindQt5.cmake:32 (find_package):
By not providing "FindQt5QuickTemplates2.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"Qt5QuickTemplates2", but CMake did not find one.
Could not find a package configuration file provided by
"Qt5QuickTemplates2" with any of the following names:
Qt5QuickTemplates2Config.cmake
qt5quicktemplates2-config.cmake
Add the installation prefix of "Qt5QuickTemplates2" to CMAKE_PREFIX_PATH or
set "Qt5QuickTemplates2_DIR" to a directory containing one of the above
files. If "Qt5QuickTemplates2" provides a separate development package or
SDK, be sure it has been installed.
Call Stack (most recent call first):
CMakeLists.txt:87 (include)
Qmake -v gives me:
QMake version 3.1
Using Qt version 5.12.2 in /Users//Qt/5.12.2/clang_64/lib
The final error is: xcodebuild: error: 'mscore.xcodeproj' does not exist.
Any ideas?
Comments
I'd like to add that the Mac version must be built and tested against Qt 5.9; the product will be built with 5.9, because 5.12 doesn't support MacOS 10.10 and 10.11, which is a business requirement.
In reply to I'd like to add that the Mac… by [DELETED] 1831606
Which is not an issue for a local build.
In reply to Which is not an issue for a… by Jojo-Schmitz
Absolutely so, but you'd be foolish to test against a platform other than that which will be shipped. You can build C++ interfaces to commercial products (i.e., violate GPL) if you want, but no one else will ever benefit from your work.
In reply to Absolutely so, but you'd be… by [DELETED] 1831606
I'm going to try with 5.9 see if it helps...
Are you sure ...Qt/5.12.2/clang_64/bin is in your PATH?
In reply to Are you sure ...Qt/5.12.2… by [DELETED] 1831606
Yep. echo $PATH gives me: :/Users/username/Qt/5.12.2/clang_64/bin
You should probably upgrade to Qt 5.12.5, which currently is the latest LTS version.
Maybe the issue is not in that templates package at all. First, this is a CMake warning and it does not lead the whole build process to be unsuccessful. With Qt 5.9 MuseScore builds successfully with this warning as there is no such package in that version of Qt. Second, Qt 5.12 still should have this package so no such warnings should be printed. Are there perhaps any other possible hints (some other error or warning messages) in CMake or other build scripts output?
In reply to Maybe the issue is not in… by dmitrio95
It isn't I think I just found the issue:
CMake Error at CMakeLists.txt:489 (MESSAGE):
Error: JACK support requested (BUILD_JACK=ON), but JACK was not found
I have jack installed.... and jackd -V gives me:
jackd version 0.125.0 tmpdir /tmp protocol 25
So it all seems good... any ideas?
In reply to It isn't I think I just… by Borziborz
Do you have the JACK sources/lib installed via brew as required?
In reply to Do you have the JACK sources… by [DELETED] 1831606
Yep
In reply to It isn't I think I just… by Borziborz
In order to build with JACK support you should probably need also JACK header files installed somewhere where CMake can find them. Do you have them on your system?
In reply to In order to build with JACK… by dmitrio95
Where can I check/ where can I add them?
In reply to Where can I check/ where can… by Borziborz
See https://musescore.org/en/handbook/developers-handbook/compilation/compi…, step 4:
$ brew install libogg libsndfile libvorbis pkg-config portaudio jack lame cmake gitAnd/or step 5:
$ sudo port install git libsndfile pkgconfig lame portaudio jack cmakeIn reply to See https://musescore.org/en… by Jojo-Schmitz
I have already installed it with brew
By the way, MacOS 10.15 (Catalina) was released yesterday (I'm running in it). I have not tried building MuseScore, but the MS ReleaseCandidate seems to run without problems (so far).
In reply to By the way, MacOS 10.15 … by [DELETED] 1831606
I'm still on 10.14. How are you finding the stability and performance of 10.15 BTW?
In reply to I'm still on 10.14. How are… by Borziborz
So far (less than a day), seems expectably stable and performant. The installation took about an hour, the usual stage-show of auto-reboots and silences. Significantly, the first 15 minutes of it took place "online" (i.e., before the first reboot). The system has to be told to permit MuseScore, or Terminal, for that matter, to be allowed to access user parts of the file system, which is surprising at first. The only real problem i've had so far is the System Preferences applet insisting I "sign up" with iCloud, and the red "notification" tag isn't going away until I do, but I refuse to (I tried going there many years ago and it started removing files from my machine and see no evidence it won't do that again). So the red tag persists.
In reply to So far (less than a day),… by [DELETED] 1831606
Seems that permission issue came up before, see https://musescore.org/en/node/292218 and https://musescore.org/en/node/294213
Might be something we need to add to https://musescore.org/en/handbook/3/install-macos and/or https://musescore.org/en/handbook/3/known-incompatibilities ?
In reply to So far (less than a day),… by [DELETED] 1831606
Please double-check my update to the macOS install handbook page
In reply to So far (less than a day),… by [DELETED] 1831606
Also, having to add "Terminal" (/Applications/Utilities/Terminal.app) to the list of apps permitted to access "full disk" is necessary if you indulge in the use of command-line apps and scripts.
In reply to Also, having to add … by [DELETED] 1831606
Hmm, so that may need to get added to https://musescore.org/en/handbook/3/revert-factory-settings#instruction… and probably https://musescore.org/en/handbook/3/command-line-options too then?
In reply to Hmm, so that may need to get… by Jojo-Schmitz
I don't know if it will follow the rules for "musescore" or for "terminal" in that case, and I'm not willing to break it to find out ... You can't even use 'cp' in a terminal window if you haven't enabled file system access in Terminal, though.
Warning: this does not remove the Cmake warning, it just makes the build display the palettes correctly.
![1.png]( "1.png")
![2.png]( "2.png")
Just resolved the problem by copying these two files in the install directory.
Were copied:
Hope this helps