Clear/complete instructions on how to build in Windows 10?

• May 21, 2021 - 10:43

So I've looked through https://github.com/musescore/MuseScore/wiki/Set-up-developer-environment but I can't actually see a clear set of steps as to how to build under Windows 10.
Obviously I've cloned the git repo, and I've tried running both msvc_build (I have both VS 2017 and 2019 installed, tried from both respective developer command prompts) and ninja_build but no go with either.
As it is I'm pretty sure I didn't actually install C++ support for VS (I didn't need it at the time), but there's nothing clarifying that I even need VS at all (as opposed to gcc etc.). Is there some documentation I'm missing?


Comments

In reply to by Dylan Nicholson1

Stuck on trying to load the Musescore folder as a solution:

---------------------------
Microsoft Visual Studio
---------------------------
The 'VCManagedPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\dylan.nicholson\AppData\Roaming\Microsoft\VisualStudio\16.0_0704d1e5\ActivityLog.xml'.

Said file contains stuff like:

Still unable to load MEF component DLL: Could not load file or assembly 'Microsoft.VisualStudio.VisualC.Utilities, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The module was expected to contain an assembly manifest.
    C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CLIENT\Microsoft.VisualStudio.CMake.Client.dll

In reply to by Marc Sabatella

It would've taken about 6-7 hours for me using the default mirror at the speed it was going. But I accidentally selected the wrong option on one screen, which caused some very strange errors in Visual Studio when I tried to build. Eventually worked out that I'd set up the PATH incorrectly and was missing a component, but couldn't readily figure out how to go and add just that component, even once I had, it was going to take another 5 or 6 hours using the default mirror.
Point is, if it's known exactly what options are needed etc., is there a reason we can't just have a script that's already set up ready to go? But actually when I tried to run the qt installer using various options to skip license confirmations etc. it seems they were just ignored.

But...update...I have now built MuseScore4.exe!

Unfortunately it doesn't run (can't find a libsndxxx.dll), but hopefully I can figure that out...

Do you still have an unanswered question? Please log in first to post your question.