Just use build.qtc, but remove it first to get rid of old build remains
---- Sideways Skullfinger schrieb ----
>First attempt today was to change the build directory from build.qtc to
>build. That is the difference. For some reason CMake is failing on this
>toolchain file when I set the build dir to build.qtc.
>
>I have searched the project for TOOLCHAIN and build.qtc and no results.
>Do I need to use build.qtc? Why? What is going wrong here? I used
>build.qtc with Qt 5.6.
>
>Also, Qt is not saving my Build Steps changes. It adds the second step,
>but both steps revert from -lrelease/-install to -all every time I close
>and reopen Qt.
>
>
>On 5/10/2018 9:33 PM, Sideways Skullfinger wrote:
>> I forgot to include the command line itself:
>>
>> Running "C:\Program Files\CMake\bin\cmake.exe -E server
>> "--pipe=\\.\pipe\{cca95612-383f-4ae5-a3d2-ae8b1b462784}"
>> --experimental" in Z:\MuseScore\build.
>>
>>
>>
>> On 5/10/2018 9:18 PM, Sideways Skullfinger wrote:
>>> Hmmm. It's not apparent to me. It's not in the kit settings CMake
>>> Configuration field, or any CMake options. CMAKE_TOOLCHAIN_FILE is a
>>> command line option. Here is the command line that Qt is running. I
>>> don't know why it's using --experimental or -E server or --pipe. I
>>> don't see where to change those in Qt, but there must be a place. It
>>> doesn't seem to be tied in with the Build Steps command line options.
>>>
>>> It's late here and I'm signing off for the day, but I think the only
>>> way to find it is to comment out that shared code temporarily, then
>>> hopefully complete the CMake configuration and get the full Build
>>> pane list for this Debug config. At that point I would hope see
>>> CMAKE_TOOLCHAIN_FILE in that list and disable it in the configuration.
>>>
>>> On 5/10/2018 8:55 PM, Joachim Schmitz wrote:
>>>>
>>>> It used to be an extra step to add this, in QtCreator, and there is
>>>> the place to remove it.
>>>>
>>>>
>>>>
>>>> ---- Sideways Skullfinger schrieb ----
>>>>
>>>> Where do I do that? I don't find it in CMakesLists.txt
>>>> <http://CMakesLists.txt>, or anywhere else in the project.
>>>> Qt isn't displaying a list of things in the Build pane because it
>>>> fails to configure. I don't see it in the Build list for my Release
>>>> config.
>>>>
>>>> On 5/10/2018 8:48 PM, Joachim Schmitz wrote:
>>>>>
>>>>> I don't think this relates to the cmake version.
>>>>> You need to remove the CMAKE_TOOLCHAIN_FILE from your configuration
>>>>>
>>>>>
>>>>>
>>>>> ---- Sideways Skullfinger schrieb ----
>>>>>
>>>>> CMakeDetermineSystem.cmake <http://CMakeDetermineSystem.cmake:100>
>>>>> is a CMake shared file, and there must be a difference here with my
>>>>> installed CMake 3.11 versus 3.10. Another version I jumped.
>>>>>
>>>>> I'll comment out this if block in that file and see if everything
>>>>> else works. Otherwise I'll regress to CMake 3.10.
>>>>>
>>>>> On 5/10/2018 8:37 PM, Joachim Schmitz wrote:
>>>>>>
>>>>>> This file does not exist anymore in the master branch.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---- Sideways Skullfinger schrieb ----
>>>>>>
>>>>>> Qt 5.9.5 <tel:5.9.5> is installed. I have edited my Qt.bat
>>>>>> <http://Qt.bat> file. I can configure a
>>>>>> Release build, but Debug still gives me this error:
>>>>>>
>>>>>> C:\Program
>>>>>> Files\CMake\share\cmake-3.11\Modules\CMakeDetermineSystem.cmake:100
>>>>>> <http://CMakeDetermineSystem.cmake:100>:
>>>>>> error: Could not find toolchain file: build/mingw32.mingw.cmake
>>>>>> <http://mingw32.mingw.cmake>
>>>>>> CMakeLists.txt:20 <http://CMakeLists.txt:20> (project)
>>>>>>
>>>>>> This is the relevant if() block in CMakeDetermineSystem.cmake
>>>>>> <http://CMakeDetermineSystem.cmake>, lines 97-102:
>>>>>>
>>>>>> # if a toolchain file is used, the user wants to cross compile.
>>>>>> # in this case read the toolchain file and keep the
>>>>>> CMAKE_HOST_SYSTEM_*
>>>>>> # variables around so they can be used in CMakeLists.txt
>>>>>> <http://CMakeLists.txt>.
>>>>>> # In all other cases, the host and target platform are the same.
>>>>>> if(CMAKE_TOOLCHAIN_FILE)
>>>>>> # at first try to load it as path relative to the directory from
>>>>>> which cmake has been run
>>>>>> include("${CMAKE_BINARY_DIR}/${CMAKE_TOOLCHAIN_FILE}" OPTIONAL
>>>>>> RESULT_VARIABLE _INCLUDED_TOOLCHAIN_FILE)
>>>>>> if(NOT _INCLUDED_TOOLCHAIN_FILE)
>>>>>> # if the file isn't found there, check the default locations
>>>>>> include("${CMAKE_TOOLCHAIN_FILE}" OPTIONAL RESULT_VARIABLE
>>>>>> _INCLUDED_TOOLCHAIN_FILE)
>>>>>> endif()
>>>>>>
>>>>>> if(_INCLUDED_TOOLCHAIN_FILE)
>>>>>> set(CMAKE_TOOLCHAIN_FILE "${_INCLUDED_TOOLCHAIN_FILE}" CACHE
>>>>>> FILEPATH "The CMake toolchain file" FORCE)
>>>>>> else()
>>>>>> message(FATAL_ERROR "Could not find toolchain file:
>>>>>> ${CMAKE_TOOLCHAIN_FILE}")
>>>>>> set(CMAKE_TOOLCHAIN_FILE "NOTFOUND" CACHE FILEPATH "The CMake
>>>>>> toolchain file" FORCE)
>>>>>> endif()
>>>>>> endif()
>>>>>>
>>>>>> I am not proficient in CMake, and have not been able to see why
>>>>>> this is
>>>>>> happening in Debug and not Release. AFAIK the only difference
>>>>>> between
>>>>>> Release and Debug is the build vs. build.qtc <http://build.qtc>
>>>>>> directories.
>>>>>>
>>>>>> The missing filename is suspicious too:mingw32.mingw.cmake
>>>>>> <http://mingw32.mingw.cmake>
>>>>>>
>>>>>> Thanks in advance for any insights.
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>> engaging tech sites, Slashdot.org <http://Slashdot.org>!
>>>>>> http://sdm.link/slashdot
>>>>>> _______________________________________________
>>>>>> Mscore-developer mailing list
>>>>>> Mscore-developer@lists.sourceforge.net
>>>>>> <mailto:Mscore-developer@lists.sourceforge.net>
>>>>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org!http://sdm.link/slashdot
>>>
>>>
>>> _______________________________________________
>>> Mscore-developer mailing list
>>> Mscore-developer@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> _______________________________________________
>> Mscore-developer mailing list
>> Mscore-developer@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>
>
>------------------------------------------------------------------------------
>Check out the vibrant tech community on one of the world's most
>engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>_______________________________________________
>Mscore-developer mailing list
>Mscore-developer@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/mscore-developer
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
