Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
MuseScore developer wannabe trying to compile the master branch of MuseScore. using Qt Creator on Windows 10. I followed the instructions at https://musescore.org/en/developers-handbook/compilation/compile-instructions-windows-mingw-git and on starting a debug build, I get 1 Issue: [CmakeFiles/lrelease] Error 1. I have no idea what the error might be since all I am doing is following a recipe, have never worked with Qt before and don’t find “Error 1” to be a helpful error message.
Here’s what I did:

• 7-zip was already installed on my system.
• I downloaded the Qt Online Installer, selected the checkboxes shown in the instructions and installed Qt and MinGW. In installed Qt in C:\PF86\Qt, which is a link to C:\Program Files (x86)\Qt.
• I did not change my %PATH%, choosing to use the Qt.bat file listed later.
• I downloaded Cmake 3.5.2 and installed it in C:\PF86\Cmake. I did not add it to my %PATH%.
• I cloned MuseScore to E:\MuseScore.
• I edited E:\MuseScore \build\mingw32.mingw.cmake to correct the path from C:/Qt to C:/PF86/Qt.
• I  created Qt.bat as described in the instructions, but with the necessary path changes.
• I installed the 32-bit version of Jack.
• I downloaded Qt-additions.zip and unpacked it, making sure the files wound up in the right portion of the Qt package (in C:\F86\Qt\Tools\mingw492_32 in my case).
• I then followed the instructions for compiling using the Qt Creator IDE:
• I started the Qt.bat script.
• I selected File / Open File or Project…
• I selected the CmakeLists.txt file from the top of the MuseScore folder.
• I did not get a “pathwizard”, whatever that is.
• I selected Projects from the sidebar and clicked on Build.
• I entered E:/MuseScore/build.qtc as the build directory.
• I clicked on Run Cmake… and ran Cmake with the arguments -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=../win32install.
• I expanded the Build Steps and selected the lrelease target.
• I clicked on Run at the top.
• I clicked on Add Deploy Step and selected the install target.
• I clicked on the Add button for the Run configuration, selected Custom Process Step and set the executable to %{sourceDir}\win32install\bin\MuseScore.exe.

That’s all I did for setup. I then selected  Debug / Start Debugging / Start Debugging and received my single issue of Error 1.
Any help appreciated.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

lasconic
Administrator
Hi,

We would need a little bit more of your build log to get more chance to catch the issue.
My first though would be that your Qt.bat is not good and Qt bin directory is not in the path. When the build process try to run lrelease (which is one of the executable in this bin directory), it can't find it and so it fails.

lasconic

2016-04-18 6:46 GMT+02:00 freixas <[hidden email]>:
MuseScore developer wannabe trying to compile the master branch of MuseScore.
using Qt Creator on Windows 10. I followed the instructions at
https://musescore.org/en/developers-handbook/compilation/compile-instructions-windows-mingw-git
and on starting a debug build, I get 1 Issue: [CmakeFiles/lrelease] Error 1.
I have no idea what the error might be since all I am doing is following a
recipe, have never worked with Qt before and don’t find “Error 1” to be a
helpful error message.
Here’s what I did:

•       7-zip was already installed on my system.
•       I downloaded the Qt Online Installer, selected the checkboxes shown in the
instructions and installed Qt and MinGW. In installed Qt in C:\PF86\Qt,
which is a link to C:\Program Files (x86)\Qt.
•       I did not change my %PATH%, choosing to use the Qt.bat file listed later.
•       I downloaded Cmake 3.5.2 and installed it in C:\PF86\Cmake. I did not add
it to my %PATH%.
•       I cloned MuseScore to E:\MuseScore.
•       I edited E:\MuseScore \build\mingw32.mingw.cmake to correct the path from
C:/Qt to C:/PF86/Qt.
•       I  created Qt.bat as described in the instructions, but with the necessary
path changes.
•       I installed the 32-bit version of Jack.
•       I downloaded Qt-additions.zip and unpacked it, making sure the files wound
up in the right portion of the Qt package (in C:\F86\Qt\Tools\mingw492_32 in
my case).
•       I then followed the instructions for compiling using the Qt Creator IDE:
•       I started the Qt.bat script.
•       I selected File / Open File or Project…
•       I selected the CmakeLists.txt file from the top of the MuseScore folder.
•       I did not get a “pathwizard”, whatever that is.
•       I selected Projects from the sidebar and clicked on Build.
•       I entered E:/MuseScore/build.qtc as the build directory.
•       I clicked on Run Cmake… and ran Cmake with the arguments
-DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=../win32install.
•       I expanded the Build Steps and selected the lrelease target.
•       I clicked on Run at the top.
•       I clicked on Add Deploy Step and selected the install target.
•       I clicked on the Add button for the Run configuration, selected Custom
Process Step and set the executable to
%{sourceDir}\win32install\bin\MuseScore.exe.

That’s all I did for setup. I then selected  Debug / Start Debugging / Start
Debugging and received my single issue of Error 1.
Any help appreciated.




--
View this message in context: http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-first-compilation-attempt-tp7579826.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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

jonEnquist
In reply to this post by freixas
Well, I applaud your creativity in creating a link without spaces in the name.  As a newbie myself, that approach didn't occur to me.

(I simply used the defaults, and installed to C:\Qt)
I strongly suspect that a "linked" directory name in your path(s) is the culprit.  Symbolic links are not a good choice in cross platform development (or so I have read.)

As an alternative to starting from scratch, and using defaults, I would suggest replacing your "PF86" (linked) directory name with "progra~2" (the "non 8dot3" name for "program files (x86)"  (if you use "dir /X" on windows 10, you will see alternate names for directory/file names which are long, or contain spaces.)

If you don't get the "pathwizard" when you open your project in Qt Creator, select "Projects" (on the left sidebar, change your build directory as needed, and select "Run Cmake"

Otherwise, "Error 1" is not coming from MuseScore, 
I would check the forums for Qt, or Mingw.

HTH  


On Sun, Apr 17, 2016 at 11:46 PM, freixas <[hidden email]> wrote:
MuseScore developer wannabe trying to compile the master branch of MuseScore.
<snip>

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

Marc Sabatella
From within QtCreator, be sure to check the Compile Output tab, not just the Issues tab at the bottom of the screen. The Issues shows only a summary, which indeed sometimes is not helpful - it tends to be useful more once you have a basically working build and you have only "regular" compile errors, not something wrong with the build environment. The Compile Output tab shows the full log.

On Mon, Apr 18, 2016 at 6:13 AM Jon Enquist <[hidden email]> wrote:
Well, I applaud your creativity in creating a link without spaces in the name.  As a newbie myself, that approach didn't occur to me.

(I simply used the defaults, and installed to C:\Qt)
I strongly suspect that a "linked" directory name in your path(s) is the culprit.  Symbolic links are not a good choice in cross platform development (or so I have read.)

As an alternative to starting from scratch, and using defaults, I would suggest replacing your "PF86" (linked) directory name with "progra~2" (the "non 8dot3" name for "program files (x86)"  (if you use "dir /X" on windows 10, you will see alternate names for directory/file names which are long, or contain spaces.)

If you don't get the "pathwizard" when you open your project in Qt Creator, select "Projects" (on the left sidebar, change your build directory as needed, and select "Run Cmake"

Otherwise, "Error 1" is not coming from MuseScore, 
I would check the forums for Qt, or Mingw.

HTH  


On Sun, Apr 17, 2016 at 11:46 PM, freixas <[hidden email]> wrote:
MuseScore developer wannabe trying to compile the master branch of MuseScore.
<snip>
------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
In reply to this post by freixas
Thanks for your patience. I started my developer life working on Sun workstations (Linux did not exist) using RCS for source control. For the last 10 years, I have been working almost exclusively with PHP and JavaScript. I used to be pretty good with Makefiles, but that was a long time ago.

I checked out a number of your suggestions.

I double-checked the paths in Qt.bat. I found that the C:\Windows\system32 path was commented out (my error) and restored it. There are some warnings about CMake being last in the path. I think the intent is that it be after Qt, but I made sure it was at the very end.

I deleted my MuseScore folder and re-cloned it. When I use File / Open File or Project... and select the CMakeLists.txt file, I see this error reported: Cannot run "git rev-parse --git-dir E:\MuseScore" in "E:\MuseScore":  so I added C:\PF86\Git\Cmd to the path and tried again.

This time, I saw a Configure Project page and when I pressed the Configure Project button, fthe "pathfinder" appeared. I ran CMake with the arguments I'm supposed to give it, and the generated output ends with -- Build files have been written to: E:/build-MuseScore-Desktop_Qt_5_6_0_MinGW_32bit-Default. That's not right. I was supposed to change the build directory first, but was never offered an obvious place to change it.

Try again. This time I clicked on the Details button and changed the Default to E:\MuseScore\built.qtc. What about all those other "kits"? Do I edit them or do I unselect them? I decided to unselect them. Then I ran the CMake. It now ended with -- Build files have been written to: E:/MuseScore/built.qtc

So I tried to build. Thanks to Marc, I looked in the compile output window and found:

07:56:10: Running steps for project mscore...
07:56:10: Starting: "C:\PF86\Qt\Tools\mingw492_32\bin\mingw32-make.exe" lrelease
Scanning dependencies of target lrelease
The system cannot find the path specified.
CMakeFiles\lrelease.dir\build.make:56: recipe for target 'CMakeFiles/lrelease' failed
mingw32-make[3]: *** [CMakeFiles/lrelease] Error 1
CMakeFiles\Makefile2:162: recipe for target 'CMakeFiles/lrelease.dir/all' failed
mingw32-make[2]: *** [CMakeFiles/lrelease.dir/all] Error 2
CMakeFiles\Makefile2:169: recipe for target 'CMakeFiles/lrelease.dir/rule' failed
makefile:222: recipe for target 'lrelease' failed
mingw32-make[1]: *** [CMakeFiles/lrelease.dir/rule] Error 2
mingw32-make: *** [lrelease] Error 2
07:56:10: The process "C:\PF86\Qt\Tools\mingw492_32\bin\mingw32-make.exe" exited with code 2.
Error while building/deploying project mscore (kit: Desktop Qt 5.6.0 MinGW 32bit)
When executing step "Make"
07:56:10: Elapsed time: 00:00.

The target at line 56 is:

CMakeFiles/lrelease:
        E:\MuseScore\build\gen-qt-projectfile E:/MuseScore > mscore.pro
        E:\MuseScore\build\gen-qt-projectfile E:/MuseScore/share/instruments > instruments.pro
        C:\PF86\Qt\5.6\mingw49_32\bin\lrelease.exe E:/MuseScore/share/locale/*.ts

where line 56 is the line that writes to mscore.pro.

mscore.pro exists in E:\MuseScore\built.qtc. I can't find instruments.pro anywhere. I can run the first command manually (without the redirection to mscore.pro) and the output exactly matches the output of mscore.pro. No errors are reported.

Unfortunately, I can also run the second line (without redirection) and I get what looks like reasonable output.

I generated the instruments.pro by hand. I'm guessing it goes the same place as score.pro. I then ran the lrelease command by hand and all output looked reasonable.

This was all from a DOS window that had my normal path. So I tried again, this time with the same settings as from my Qt.bat file. Again, no problems.

So I decided to try to build by hand. Again using the same environment as from my Qt.bat, I moved to C:\MuseScore and ran mingw32-make -f Makefile.mingw release.  Here is the output with debug on:

if not exist build.release\nul mkdir build.release
CreateProcess(D:\Users\tony\AppData\Local\Temp\make10884-1.bat,D:\Users\tony\AppData\Local\Temp\make10884-1.bat,...)
Putting child 00E6B380 (release) PID 15149200 on the chain.
Recipe of 'release' is being run.
Live child 00E6B380 (release) PID 15149200
Main thread handle = 000000C0
The system cannot find the path specified.
Reaping losing child 00E6B380 PID 15149200
Cleaning up temp batch file D:\Users\tony\AppData\Local\Temp\make10884-1.bat
Makefile.mingw:28: recipe for target 'release' failed
mingw32-make: *** [release] Error 1
Removing child 00E6B380 PID 15149200 from chain.

The build.release folder is actually created. The win32install folder is not. The two commands in the makefile look very similar:

        if not exist build.release\nul mkdir build.release
        if not exist win32install\nul mkdir win32install

OK, so maybe my use of C:\PF86 as a link is a problem. The places where problems appear don't seem related to the C:\PF86 link. I will keep trying but maybe something obvious will occur to someone.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
In reply to this post by Marc Sabatella
I decided to try a build with Qt in the default location. It's building now. I don't know why the link hangs it up.

The build dies on the second command in this make target:

resfile.o: ../mscore/data/mscore.rc
    @$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold --progress-dir=E:\MuseScore\build.qtc\CMakeFiles --progress-num=$(CMAKE_PROGRESS_150) "Generating ../resfile.o"
    cd /d E:\MuseScore\mscore\data && -i mscore.rc -o E:/MuseScore/build.qtc/mscore.res
    cd /d E:\MuseScore\mscore\data && \home\ws\.wine\drive_c\MingW\bin\windres.exe E:/MuseScore/build.qtc/mscore.res -o E:/MuseScore/build.qtc/resfile.o

Note the "&& -i mscore.rc". As far as I can tell, this should be "... && <some path>/wrc.bat -i ...". I gather that when the makefiles are being generated, the QT_WRC_EXECUTABLE command is being set to the empty string. Not sure how to fix this.

Tony Freixas
[hidden email]


If you reply to this email, your message will be added to the discussion below:
http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-first-compilation-attempt-tp7579826p7579830.html
To unsubscribe from Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

jonEnquist
This post was updated on .
If I attempt a "Release" build from Qt, the compile output fails starting with the following:
===========
[ 51%] Generating ../resfile.o
[ 51%] Generating qrc_musescore.cpp
'-i' is not recognized as an internal or external command,
operable program or batch file.
mscore\CMakeFiles\mscore.dir\build.make:827: recipe for target 'resfile.o' failed
mingw32-make[2]: *** [resfile.o] Error 1
mingw32-make[2]: *** Waiting for unfinished jobs....
===========

Make sure you have selected a "Debug" build (which you can run "standalone, i.e. without the debugger, as long as the environment is correct, I had to modify the .bat file I use to run Qt Creator.  After my Qt 5.6 upgrade, the old .bat didn't work, although I could run from Qt.  I cut the path Qt was using from one of the debugger windows and pasted it to my MuseDebug.bat, and now I can run my development version standalone. I have attempted to attach a copy.

After selecting a Debug build, you may have to re-run cmake (from "Projects") and "Re-build" (as opposed to "Build") to ensure a clean build.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
Thanks for the help, Jon. The build process for MuseScore is complex and uses tools that I am not experienced with.

Let's try small steps.

Using Qt Creator, how does one start a "Debug" build?

I have a "Default" kit, where CMake is generated with the command line options

-DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=../win32install

This should generate Makefiles for a debug build, right?

I start the build using Debug / Start Debugging / Start Debugging.

Using this process, I get the same problem that you say you only get with the "Release" build.

------------------------------------------------------------------------------------

The compilation instructions for Windows appear to be incorrect when using Qt Creator 3.6.1.

When the CMakeLists.txt file is first opened, you enter a project configuration page. You are presented with a list of "kits": Default, Debug, Release, etc. I unselected everything except Default. Each "kit" has an associated folder. I set the release folder to E:\MuseScore\build.qtc. Then clicking on "Configure Project" brings a dialog for running CMake.

------------------------------------------------------------------------------------

The problem I'm running into comes from QT_WRC_EXECUTABLE not being set.

It appears to be defined in E:\MuseScore\build\mingw32.mingw.cmake:

${CMAKE_CURRENT_LIST_DIR}/wrc.bat)

and used in E:\MuseScore\mscore\CMakeLists.txt:

COMMAND ${QT_WRC_EXECUTABLE} -i mscore.rc -o ${PROJECT_BINARY_DIR}/mscore.res

The generated make file is mscore\CMakeFiles\mscore.dir\build.make and the result is:

resfile.o: ../mscore/data/mscore.rc
        @$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold --progress-dir=E:\MuseScore\build.qtc\CMakeFiles --progress-num=$(CMAKE_PROGRESS_150) "Generating ../resfile.o"
        cd /d E:\MuseScore\mscore\data && -i mscore.rc -o E:/MuseScore/build.qtc/mscore.res
        cd /d E:\MuseScore\mscore\data && \home\ws\.wine\drive_c\MingW\bin\windres.exe E:/MuseScore/build.qtc/mscore.res -o E:/MuseScore/build.qtc/resfile.o

Notice that wine.bat has the same problem.

Manually fixing the build.make file fixes the problem, at least until the make files are re-created:

resfile.o: ../mscore/data/mscore.rc
        @$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold --progress-dir=E:\MuseScore\build.qtc\CMakeFiles --progress-num=$(CMAKE_PROGRESS_150) "Generating ../resfile.o"
        cd /d E:\MuseScore\mscore\data && E:/MuseScore\build\wrc.bat -i mscore.rc -o E:/MuseScore/build.qtc/mscore.res
        cd /d E:\MuseScore\mscore\data && E:/MuseScore\build\wine.bat \home\ws\.wine\drive_c\MingW\bin\windres.exe E:/MuseScore/build.qtc/mscore.res -o E:/MuseScore/build.qtc/resfile.o


The build runs to 98% and then starts getting a ton of undefined references:

[ 97%] Building CXX object mscore/CMakeFiles/mscore.dir/qmledit.cpp.obj
[ 97%] Building CXX object mscore/CMakeFiles/mscore.dir/pluginManager.cpp.obj
[ 97%] Building CXX object mscore/CMakeFiles/mscore.dir/mscore_automoc.cpp.obj
[ 98%] Linking CXX executable MuseScore.exe
CMakeFiles\mscore.dir/objects.a(qrc_musescore.cpp.obj): In function `Z24qInitResources_musescorev':
E:/MuseScore/build.qtc/mscore/qrc_musescore.cpp:43033: undefined reference to `qRegisterResourceData(int, unsigned char const*, unsigned char const*, unsigned char const*)'
CMakeFiles\mscore.dir/objects.a(qrc_musescore.cpp.obj): In function `Z27qCleanupResources_musescorev':
E:/MuseScore/build.qtc/mscore/qrc_musescore.cpp:43041: undefined reference to `qUnregisterResourceData(int, unsigned char const*, unsigned char const*, unsigned char const*)'
CMakeFiles\mscore.dir/objects.a(qrc_musescorefonts-MScore.cpp.obj): In function `Z36qInitResources_musescorefonts_MScorev':
E:/MuseScore/build.qtc/mscore/qrc_musescorefonts-MScore.cpp:9763: undefined reference to `qRegisterResourceData(int, unsigned char const*, unsigned char const*, unsigned char const*)'
CMakeFiles\mscore.dir/objects.a(qrc_musescorefonts-MScore.cpp.obj): In function `Z39qCleanupResources_musescorefonts_MScorev':
E:/MuseScore/build.qtc/mscore/qrc_musescorefonts-MScore.cpp:9771: undefined reference to `qUnregisterResourceData(int, unsigned char const*, unsigned char const*, unsigned char const*)'
CMakeFiles\mscore.dir/objects.a(qrc_musescorefonts-Gootville.cpp.obj): In function `Z39qInitResources_musescorefonts_Gootvillev':
E:/MuseScore/build.qtc/mscore/qrc_musescorefonts-Gootville.cpp:5122: undefined reference to `qRegisterResourceData(int, unsigned char const*, unsigned char const*, unsigned char const*)'
CMakeFiles\mscore.dir/objects.a(qrc_musescorefonts-Gootville.cpp.obj): In function `Z42qCleanupResources_musescorefonts_Gootvillev':

... and on and on ...

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

jonEnquist
This post was updated on .
I use qt.bat to set path and environment values and then start Qt Creator, and restore my last session (and MuseScore is the only thing I'm working on, so it becomes the current open project.)

From the "Projects" tab, under "Build Settings" select "Debug" (instead of "Default") (click the down arrow and select from the list.)

Change the build directory as desired, the click on "Run CMake"

I have the following in my arguments, I don't know why it is different than the documentation:
-DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_TOOLCHAIN_FILE=build/mingw32.mingw.cmake -DCMAKE_INSTALL_PREFIX=../win32install

Then proceed with "Debug"->"Start  Debugging"->"Start Debugging (F5)"


FWIW - here are the versions I have installed: (Check especially your CMake version.)

C:\Users\janet>qtcreator -version
=====> Popup window shows "Qt Creator 3.6.1 based on Qt 5.6.0"
C:\Users\janet>cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

C:\Users\janet>g++ --version
g++ (i686-posix-dwarf-rev1, Built by MinGW-W64 project) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Users\janet>git --version
git version 2.8.1.windows.1

C:\Users\janet>doxygen --version
1.8.11

C:\Users\janet>latex --version
MiKTeX-pdfTeX 2.9.5840 (1.40.16) (MiKTeX 2.9)
Copyright (C) 1982 D. E. Knuth, (C) 1996-2014 Han The Thanh
TeX is a trademark of the American Mathematical Society.
compiled with zlib version 1.2.8; using 1.2.8
compiled with libpng version 1.6.19; using 1.6.19
compiled with poppler version 0.32.0
compiled with jpeg version 8.4
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
Hi, Jon,

Thanks for sticking with me. It looks like the CMake arguments are the key. I suspect that the Qt "kit" selection of "Debug" is not important, but I haven't tried it.

If the developers would like, I could update the Windows compilation instruction pages:
  • Correct the instructions for what happens after cloning MuseScore and opening CMakeLists.txt for the first time. This might need more testing. I suspect that the its possible to define just the "Default" kit or just the "Debug" and "Release" kits. The "Release" kit would remove the DEBUG definition from the CMake options.
  • Replace the CMake options with the version you gave me.

I think that's about it for corrections. The text could probably be edited for clarity.

I know I can just jump in edit the page. Considering how little I know about the build and the build tools, this is not something I want to do unless I know that someone with a lot more experience will check the changes.

Tony Freixas
[hidden email]


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

Jojo-Schmitz
In reply to this post by jonEnquist
The -DCMAKE_TOOLCHAIN_FILE=build/mingw32.mingw.cmake is not needed
(anymore?), leads to a warning of being unused. So I've removed it from the
instructions.

-----Original Message-----
From: jonEnquist [mailto:[hidden email]]
Sent: Thursday, April 21, 2016 5:16 AM
To: [hidden email]
Subject: Re: [Mscore-developer] Qt Creator [CmakeFiles/lrelease] Error 1 in
first compilation attempt

I use  qt.bat <http://dev-list.musescore.org/file/n7579843/qt.bat>   to *set
path and environment values* and then start Qt Creator, and restore my last
session (and MuseScore is the only thing I'm working on, so it becomes the
current open project.)

>From the "Projects" tab, under "Build Settings" select "Debug" (instead
>of
"Default") (click the down arrow and select from the list.)

Change the build directory as desired, the click on "Run CMake"

I have the following in my arguments, I don't know why it is different than
the documentation:
-DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_TOOLCHAIN_FILE=build/mingw32.mingw.cmake
-DCMAKE_INSTALL_PREFIX=../win32install

Then proceed with "Debug"->"Start  Debugging"->"Start Debugging (F5)"


FWIW - here are the versions I have installed: (Check especially your CMake
version.)

C:\Users\janet>qtcreator -version
=====> Popup window shows "Qt Creator 3.6.1 based on Qt 5.6.0"
C:\Users\janet>cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

C:\Users\janet>g++ --version
g++ (i686-posix-dwarf-rev1, Built by MinGW-W64 project) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Users\janet>git --version
git version 2.8.1.windows.1

C:\Users\janet>doxygen --version
1.8.11

C:\Users\janet>latex --version
MiKTeX-pdfTeX 2.9.5840 (1.40.16) (MiKTeX 2.9) Copyright (C) 1982 D. E.
Knuth, (C) 1996-2014 Han The Thanh TeX is a trademark of the American
Mathematical Society.
compiled with zlib version 1.2.8; using 1.2.8 compiled with libpng version
1.6.19; using 1.6.19 compiled with poppler version 0.32.0 compiled with jpeg
version 8.4

C:\Users\janet>qtcreator -version
=====> Popup window shows "Qt Creator 3.6.1 based on Qt 5.6.0"
C:\Users\janet>cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

C:\Users\janet>g++ --version
g++ (i686-posix-dwarf-rev1, Built by MinGW-W64 project) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Users\janet>git --version
git version 2.8.1.windows.1

C:\Users\janet>doxygen --version
1.8.11

C:\Users\janet>latex --version
MiKTeX-pdfTeX 2.9.5840 (1.40.16) (MiKTeX 2.9) Copyright (C) 1982 D. E.
Knuth, (C) 1996-2014 Han The Thanh TeX is a trademark of the American
Mathematical Society.
compiled with zlib version 1.2.8; using 1.2.8 compiled with libpng version
1.6.19; using 1.6.19 compiled with poppler version 0.32.0 compiled with jpeg
version 8.4





--
View this message in context:
http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-firs
t-compilation-attempt-tp7579826p7579843.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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

Jojo-Schmitz
In reply to this post by freixas
The instructions should work just fine, if followed to the letter. Note they
have recently(about a week ago) been updated to reflect the need of Qt-5.6
and some other changes minor changes

-----Original Message-----
From: freixas [mailto:[hidden email]]
Sent: Thursday, April 21, 2016 6:39 AM
To: [hidden email]
Subject: Re: [Mscore-developer] Qt Creator [CmakeFiles/lrelease] Error 1 in
first compilation attempt

Hi, Jon,

Thanks for sticking with me. It looks like the CMake arguments are the key.
I suspect that the Qt "kit" selection of "Debug" is not important, but I
haven't tried it.

If the developers would like, I could update the Windows compilation
instruction pages:

  * Correct the instructions for what happens after cloning MuseScore
    and opening CMakeLists.txt for the first time. This might need more
    testing. I suspect that the its possible to define just the
    "Default" kit or just the "Debug" and "Release" kits. The "Release"
    kit would remove the DEBUG definition from the CMake options.
  * Replace the CMake options with the version you gave me.

I think that's about it for corrections. The text could probably be edited
for clarity.

I know I can just jump in edit the page. Considering how little I know about
the build and the build tools, this is not something I want to do unless I
know that someone with a lot more experience will check the changes.

Tony Freixas
[hidden email] <mailto:[hidden email]>






--
View this message in context:
http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-firs
t-compilation-attempt-tp7579826p7579844.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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

Jojo-Schmitz
In reply to this post by jonEnquist
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...

-----Original Message-----
From: Joachim Schmitz [mailto:[hidden email]]
Sent: Thursday, April 21, 2016 12:23 PM
To: '[hidden email]'
<[hidden email]>
Subject: RE: [Mscore-developer] Qt Creator [CmakeFiles/lrelease] Error 1 in
first compilation attempt

The -DCMAKE_TOOLCHAIN_FILE=build/mingw32.mingw.cmake is not needed
(anymore?), leads to a warning of being unused. So I've removed it from the
instructions.

-----Original Message-----
From: jonEnquist [mailto:[hidden email]]
Sent: Thursday, April 21, 2016 5:16 AM
To: [hidden email]
Subject: Re: [Mscore-developer] Qt Creator [CmakeFiles/lrelease] Error 1 in
first compilation attempt

I use  qt.bat <http://dev-list.musescore.org/file/n7579843/qt.bat>   to *set
path and environment values* and then start Qt Creator, and restore my last
session (and MuseScore is the only thing I'm working on, so it becomes the
current open project.)

>From the "Projects" tab, under "Build Settings" select "Debug" (instead
>of
"Default") (click the down arrow and select from the list.)

Change the build directory as desired, the click on "Run CMake"

I have the following in my arguments, I don't know why it is different than
the documentation:
-DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_TOOLCHAIN_FILE=build/mingw32.mingw.cmake
-DCMAKE_INSTALL_PREFIX=../win32install

Then proceed with "Debug"->"Start  Debugging"->"Start Debugging (F5)"


FWIW - here are the versions I have installed: (Check especially your CMake
version.)

C:\Users\janet>qtcreator -version
=====> Popup window shows "Qt Creator 3.6.1 based on Qt 5.6.0"
C:\Users\janet>cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

C:\Users\janet>g++ --version
g++ (i686-posix-dwarf-rev1, Built by MinGW-W64 project) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Users\janet>git --version
git version 2.8.1.windows.1

C:\Users\janet>doxygen --version
1.8.11

C:\Users\janet>latex --version
MiKTeX-pdfTeX 2.9.5840 (1.40.16) (MiKTeX 2.9) Copyright (C) 1982 D. E.
Knuth, (C) 1996-2014 Han The Thanh TeX is a trademark of the American
Mathematical Society.
compiled with zlib version 1.2.8; using 1.2.8 compiled with libpng version
1.6.19; using 1.6.19 compiled with poppler version 0.32.0 compiled with jpeg
version 8.4

C:\Users\janet>qtcreator -version
=====> Popup window shows "Qt Creator 3.6.1 based on Qt 5.6.0"
C:\Users\janet>cmake --version
cmake version 3.5.1

CMake suite maintained and supported by Kitware (kitware.com/cmake).

C:\Users\janet>g++ --version
g++ (i686-posix-dwarf-rev1, Built by MinGW-W64 project) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Users\janet>git --version
git version 2.8.1.windows.1

C:\Users\janet>doxygen --version
1.8.11

C:\Users\janet>latex --version
MiKTeX-pdfTeX 2.9.5840 (1.40.16) (MiKTeX 2.9) Copyright (C) 1982 D. E.
Knuth, (C) 1996-2014 Han The Thanh TeX is a trademark of the American
Mathematical Society.
compiled with zlib version 1.2.8; using 1.2.8 compiled with libpng version
1.6.19; using 1.6.19 compiled with poppler version 0.32.0 compiled with jpeg
version 8.4





--
View this message in context:
http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-firs
t-compilation-attempt-tp7579826p7579843.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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
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
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...


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

Jojo-Schmitz
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:[hidden email]]
Sent: Thursday, April 21, 2016 1:16 PM
To: [hidden email]
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
[hidden email] <mailto:[hidden email]> 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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

jeetee
In reply to this post by freixas
freixas wrote
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.
Correct; one 'kit' is given build configuration. I myself kept two kits, Default which does a make install and a Debug one configured for running an mtest.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

jeetee
My bad, I confused 'kit' (toolchain) with build configuration (debug/release/default).
I believe freixas made the same wording error in his post
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

Jojo-Schmitz
Ah, that one. I never used something other than Default as the build config

-----Original Message-----
From: jeetee [mailto:[hidden email]]
Sent: Thursday, April 21, 2016 1:35 PM
To: [hidden email]
Subject: Re: [Mscore-developer] Qt Creator [CmakeFiles/lrelease] Error 1 in
first compilation attempt

My bad, I confused 'kit' (toolchain) with build configuration
(debug/release/default).
I believe freixas made the same wording error in his post



--
View this message in context:
http://dev-list.musescore.org/Qt-Creator-CmakeFiles-lrelease-Error-1-in-firs
t-compilation-attempt-tp7579826p7579851.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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

jonEnquist
In reply to this post by jonEnquist
Another worthwhile step would be to use the command line compile.  That would help determine
whether the problems you are experiencing are related to the configuration of Qt Creator, or not.
(MarcSabatella reported issues with CMakeLists.txt not being up to date on a local repo, think that was
a different thread...)

Make a copy of the Qt.bat file, (previous post) and replace the "start /low qtcreator..." line
with "cmd".  Save it as, say, MScoreCmd.bat .

Run MScoreCmd.bat to set your path and environment values and give you a command prompt.
Change to your local repo (source directory for MuseScore) and enter the compile command given
in the developer's handbook:

mingw32-make -f Makefile.mingw debug

(Worked on my machine last night, worth a try...)
 
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Qt Creator [CmakeFiles/lrelease] Error 1 in first compilation attempt

freixas
In reply to this post by jeetee
Perhaps some images would help.  I hope the developer's mailing list can handle inline images! If the images are missing, I'll try to add them, so be patient.

Delete the CMakeLists.txt.user file and open Qt Creator. Here's what I get. Notice the use of the word "kits". Also, there is a check box labeled "Select all kits".

Two points:
  • This page is not mentioned in the compilation instructions as far as I can tell.
  • The correct word to use is "kits" because that is what Qt calls the different build configurations. The instructions could say that a kit is build configuration.


Here is what I see if I click on the Details box. There are five kits and no instructions as to how these should be set up.

Also, the build path needs to be given here, not in the CMake run dialog.



Click on Configure Project and you get the Run CMake dialog. I have never heard of a "pathfinder" although I could make some guesses as to what it might be. As this dialog has no Browse button, the term "pathfinder" would be confusing anyway. My guess is that you are documenting some process from an earlier version of Qt.

This dialog does not ask for the path to CMake.



The instructions should be updated to reflect the above reality. That said, although I was puzzled by this, it wasn't hard to figure out what to do. However, I was unable to get past the incorrect CMake arguments given in the instructions until Jon clued me in.

Let me know if you need any further clarification.

Tony Freixas
[hidden email]

On 4/21/2016 4:34 AM, jeetee [via MuseScore Developer] wrote:
My bad, I confused 'kit' (toolchain) with build configuration (debug/release/default).
I believe freixas made the same wording error in his post

Loading...