Well, I was offered that MuseScore-build and had to override it to MuseScore\build.qtc. Not sure what you're talking about reg. kits? I have 2 kits, one for Qt.5.4 (as needed for MuseScore 2.0.x) and another for Qt-5.6.
-----Original Message----- From: freixas [mailto:[email protected]] Sent: Thursday, April 21, 2016 1:16 PM To: [email protected] Subject: Re: [Mscore-developer] Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt Hi, Jojo-Schmitz, Thanks for checking into -DCMAKE_TOOLCHAIN_FILE. As I noted, the instructions also have a problem the first time you open the project. Clone a new tree and open up the project. You will not be offered a "pathwizard" and the offered build location won't be MuseScore-build. At least, that's never how it worked for me. After opening the project for the first time, I was shown a page that had a checkmark for something like "Select all kits". Pressing a "Details" button, brings up five kits: Default, Debug, Release, Release with Debug Symbols and Minimum Build (I'm working from memory here). There are five different build locations, each one with a really long, descriptive name. I suspect that only the Default kit is needed, so the others can be unchecked. Then here is where the build path is set to MuseScore/build.qtc. After that, you need to click on "Configure Project" to get the CMake run options. I don't remember having to choose a CMake executable. I was able to enter the CMake arguments, though, and run CMake. After this is done, the Project Configuration page changes to a form that matches the instructions. If this is not what happens on your system, then I suspect that your system may have some left-over configuration and you are not starting clean. In my case, I had never installed Qt or cloned MuseScore. The instructions for the set-up of Qt Creator don't quite track what happens from where it says "Now it will take you to..." up through bullets 1-3. The rest of the section is fine. It would be nice to know whether to just use the Default kit, or set up all five kits. If you can't reproduce this, I could send you some screen shots. Tony Freixas [email protected] <mailto:[email protected]> On 4/21/2016 3:44 AM, Jojo-Schmitz [via MuseScore Developer] wrote: > Forget about it, -DCMAKE_TOOLCHAIN_FILE=build/mingw32.mingw.cmake is > needed, at least the first time (thanks lasconic and jeetee). I'll add > it back to the instructions, sorry about this, I was sure to have > checked that, but apparently did not... > > Any I'm getting the very same error about -I not being a valid command... > -- View this message in context: http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-firs t-compilation-attempt-tp7579826p7579848.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
