Problems installing on Linux

• Aug 23, 2018 - 08:04
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Once
Status
closed
Regression
No
Workaround
No
Project
MuseScore

The mscore/CMakeLists.txt file, as it is, doesn't install on my computer. Instead, I have to comment out lines 620-631 (incl.), after which it will install fine. I suggest that a fix might be to change line 619 from:

if (NOT APPLE AND USE_WEBENGINE)

to

if (NOT APPLE AND NOT LN_EXECUTABLE AND USE_WEBENGINE)

and then changing line 632 respectively to

endif(NOT APPLE AND NOT LN_EXECUTABLE AND USE_WEBENGINE)

This fixes the problem for me. Tested on Ubuntu 18.04, x86_64. Qt (5.9.5) and all MuseScore dependencies were installed using apt. Since I don't know the ins and outs about how CMake works, would this fix be an ok one to make permanently?

Comments

• Sep 1, 2018 - 00:54

The fix suggested by TheOtherJThistle works for me on Fedora 28 too. I believe the fix by dmitrio95 would as well but I haven't tested it due to my lack of knowledge of cmake.

Reply

• Nov 13, 2018 - 13:01
Severity S3 - Major ⇒ S2 - Critical
Status ⇒ PR created
Frequency ⇒ Few
Priority ⇒ P2 - Medium
Regression ⇒ No
Reproducibility ⇒ Once
Workaround ⇒ No

@dmitrio95, are you building MuseScore without the mentioned fix?

Reply

• Nov 13, 2018 - 14:36

Yes, I use no modifications to MuseScore code to build and install MuseScore. That is because I use Qt version installed with the installer from Qt website while people affected by this bug are probably using Qt versions as packaged by their distributions' maintainers. In such a case all installed files are placed in different directory which is handled by Qt but not handled by our CMake files (see my other comment). Still we are better to figure out first whether we actually need to include some files to our installation.

Reply

• Nov 13, 2018 - 15:03

If you are right, so there is no an issue at all. We have instructions which recommend the flow. If someone creates his/her own flow, we shouldn't apply changes to the codebase to support it.

Reply

• Nov 13, 2018 - 19:49

I believe this is an issue as this would make package maintainers develop these fixes independently instead of fixing this once and in one place. This also creates unnecessary problems for those who would like to compile for some reasons MuseScore from the source code. The only reason I use Qt official installer is versions mismatch between Qt version available in Debian 9 and Qt version required for MuseScore.

In fact I had some drafts for the solution of this problem based on using locations obtained from qmake properties so I could review them again and propose that solution as a new pull request. Still if not including some of Qt libraries in MuseScore installation won't damage all MuseScore functionality perhaps this could be the simpler solution.

Reply