Both have a build and install directory only their own ---- Sideways Skullfinger schrieb ----
>But the build and install directories change, so you have to reconfigure >at least that part. > >\On 11/27/2018 3:02 PM, Joachim Schmitz wrote: >> >> There is no special settings needed to build with MSVC and QtCreator's >> Mingw from within the same source repo. At least I remember none. >> >> >> >> ---- Sideways Skullfinger schrieb ---- >> >> The VS2017 Compile instructions >> <https://musescore.org/en/handbook/developers-handbook/compilation/compile-instructions-windows-visual-studio-2017> >> >> have been updated to correct errors and reflect my experience >> "undergoing the procedure". >> >> The only thing missing are instructions on how to reconfigure Qt, so >> that you can run the two side-by-side, as Jojo does. If I ever bother >> to do that setup, I'll add it to the instructions. So far I have not >> had an urgent enough need. I do know that it requires >> reconfiguration, otherwise it causes a specific git glitch that I >> experienced here: https://musescore.org/en/node/278761 >> >> >> On 11/24/2018 5:09 PM, Sideways Skullfinger wrote: >>> Jojo wrote: >>> "Only with MSVC 64bit we will have WebEngine, needed for the online >>> part of the start center." >>> Though that can be done with Qt 5.12 and Qt Creator. Beyond that I >>> don't know the rationale for any official change of tools. I'm just >>> trying to use the most normal, median setup, so that I have as few >>> problems as possible going forward. Depending on my experience over >>> the next couple of days I might move back to Qt Creator. If editing >>> .ui files is the only thing I need to do in Qt Creator, then that's >>> not a big deal, as I rarely do that. >>> >>> I have experience with VS2017 from a Web Audio project I did a year >>> ago, so for me it's a consolidation of tools, not a learning of new >>> tools. I am doing a bunch of different development in different >>> languages, and while Qt Creator has a great editor for C++, it's not >>> so great for JavaScript, CSS, and other stuff I'm doing. On the >>> other hand, my experience using VS2017 as a JavaScript editor has not >>> been positive during the past day or so, which is disappointing. >>> Regardless, one less IDE on my PC is a good thing, so I'm still >>> cautiously optimistic about this move to VS2017. >>> >>> On 11/24/2018 4:46 PM, Marc Sabatella wrote: >>>> I am on Windows 10 and plan to continue using mingw & QtCreator >>>> until it no longer seems viable. I can't imagine any possible >>>> benefit that would justify the pain of installing and learning new >>>> tools. I assume there was some reason for the change, but I don't >>>> recall it ever being explained. >>>> >>>> Marc >>>> >>>> On Sat, Nov 24, 2018 at 3:14 PM Sideways Skullfinger >>>> <sidew...@sidewaysskullfinger.com >>>> <mailto:sidew...@sidewaysskullfinger.com>> wrote: >>>> >>>> I already have a reason to edit one of the .ui files, which >>>> causes the Qt extension to activate inside VS2017. So far all >>>> it does is crash VS2017. >>>> >>>> Jojo - are you able to edit .ui files inside VS2017? Or is that >>>> one of the reasons you still use Qt Creator? >>>> >>>> For now I'm going to edit this file in Qt Creator and then >>>> reopen VS2017 after I'm done. >>>> >>>> >>>> >>>> On 11/23/2018 8:56 AM, Sideways Skullfinger wrote: >>>>> To end this thread on a note that might interest the email list: >>>>> What configuration are you using personally right now? It >>>>> sounds like you're still using mingw, and that MuseScore still >>>>> supports building with mingw. Is there a timeline for ending >>>>> that support and only supporting MSVC inside Visual Studio? >>>>> >>>>> >>>>> On 11/22/2018 11:43 PM, Joachim Schmitz wrote: >>>>>> >>>>>> Yes, and they should be current >>>>>> >>>>>> >>>>>> >>>>>> ---- Sideways Skullfinger schrieb ---- >>>>>> >>>>>> To make sure I understand - "the former" is VS 2017, which is >>>>>> the official Windows build method now, so I should switch to it. >>>>>> OK. I see instructions for that here: >>>>>> >>>>>> https://musescore.org/en/handbook/developers-handbook/compilation/compile-instructions-windows-visual-studio-2017 >>>>>> Are those up-to-date? Or maybe nothing has changed for those >>>>>> instructions. >>>>>> I just finished installing Qt 5.12 ... >>>>>> >>>>>> On 11/22/2018 4:33 PM, Joachim Schmitz wrote: >>>>>>> >>>>>>> The former. The latter is still a todo.... >>>>>>> >>>>>>> >>>>>>> >>>>>>> ---- Sideways Skullfinger schrieb ---- >>>>>>> >>>>>>> So I should stop using Qt and switch to MSVC? I have Visual >>>>>>> Studio 2017 installed for another project. I could switch. >>>>>>> Or is this MSVC inside Qt Creator? >>>>>>> >>>>>>> On 11/22/2018 4:07 PM, Joachim Schmitz wrote: >>>>>>>> >>>>>>>> Of course I meant "in time"... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ---- Joachim Schmitz schrieb ---- >>>>>>>> >>>>>>>> Ah, good to know, maybe just in tile for musescore 3 beta ;-) >>>>>>>> Note though that the official way is no longer via MinGW but >>>>>>>> via MSVC >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ---- Sideways Skullfinger schrieb ---- >>>>>>>> >>>>>>>> I am updating to the final RC right now. It was released >>>>>>>> several hours ago. >>>>>>>> >>>>>>>> On 11/22/2018 3:57 PM, Joachim Schmitz wrote: >>>>>>>>> >>>>>>>>> I'm using it ever since the first Alpha, RC is expected any >>>>>>>>> day now, final in the first week of December >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ---- Sideways Skullfinger schrieb ---- >>>>>>>>> >>>>>>>>> OK. My deploy steps seem to have gotten toasted in the >>>>>>>>> process too. I'm having trouble going back to building my >>>>>>>>> previously committed, unrebased code. I've been hoping for >>>>>>>>> a real 64 bit version of this to come along, so I think >>>>>>>>> I'll try 5.12, if that's an approved version for MuseScore. >>>>>>>>> I just looked at the handbook and there it is, as of 3 >>>>>>>>> weeks ago 5.12 and 64 bit is available. OK. I'll install >>>>>>>>> Qt and follow instructions again. >>>>>>>>> Thanks! >>>>>>>>> >>>>>>>>> On 11/22/2018 3:17 PM, Joachim Schmitz wrote: >>>>>>>>>> >>>>>>>>>> You need to set BUILD_64 to false, or use Qt 5.12, which >>>>>>>>>> has a 64bit mingw >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ---- Sideways Skullfinger schrieb ---- >>>>>>>>>> >>>>>>>>>> Yesterday I was building with off of a master that was a >>>>>>>>>> few months >>>>>>>>>> old. Today with the new master I am getting this error at >>>>>>>>>> the very end >>>>>>>>>> of the build: >>>>>>>>>> >>>>>>>>>> CMake Error at mscore/cmake_install.cmake:46 >>>>>>>>>> <http://cmake_install.cmake:46> (file): >>>>>>>>>> file INSTALL cannot find >>>>>>>>>> "C:/Qt/Tools/mingw530_32/bin/libgcc_s_seh-1.dll >>>>>>>>>> <http://libgcc_s_seh-1.dll>". >>>>>>>>>> >>>>>>>>>> I am running Qt 5.9.5 <tel:5.9.5>, and you can see the >>>>>>>>>> mingw version in the error >>>>>>>>>> message. I have not compiled MuseScore in the past few >>>>>>>>>> months, did I >>>>>>>>>> miss something? Do I need to change my install >>>>>>>>>> configuration, and if >>>>>>>>>> so, how do I do that? Or do I need to find a copy of this >>>>>>>>>> dll file and >>>>>>>>>> copy it into this mingw folder? >>>>>>>>>> >>>>>>>>>> Thanks! >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Mscore-developer mailing list >>>>>>>>>> Mscore-developer@lists.sourceforge.net >>>>>>>>>> <mailto:Mscore-developer@lists.sourceforge.net> >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Mscore-developer mailing list >>>>> Mscore-developer@lists.sourceforge.net >>>>> <mailto:Mscore-developer@lists.sourceforge.net> >>>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer >>>> >>>> >>>> _______________________________________________ >>>> Mscore-developer mailing list >>>> Mscore-developer@lists.sourceforge.net >>>> <mailto:Mscore-developer@lists.sourceforge.net> >>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Mscore-developer mailing list >>>> Mscore-developer@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer >>> >>> >>> >>> >>> _______________________________________________ >>> Mscore-developer mailing list >>> Mscore-developer@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/mscore-developer >> >> >
_______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
