From helmut.muelner at gmail.com Thu Jun 1 16:28:48 2017 From: helmut.muelner at gmail.com (=?iso-8859-1?Q?Helmut_M=FClner?=) Date: Thu, 1 Jun 2017 16:28:48 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support Message-ID: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> Hi, [second try, first sent with wrong user account] I have two problems: 1. Build a project mit cmake and Qt 5.8.0 (msvc2013-64) works, but I cannot debug qml (Enable QML in Debugger Settings is checked, but Application Output says: QML Debugger: Ignoring "-qmljsdebugger=port:64821,block,services:DebugMessages,QmlDebugger,V8Debugg er,QmlInspector". Debugging has not been enabled. 2. If I select the kit "Qt 5.9.0 (msvc2017-64), I get the following in "General Messages": Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): No CMAKE_C_COMPILER could be found. Can anybody tell me what to do? Cheers Helmut -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristian.adam at gmail.com Thu Jun 1 16:48:42 2017 From: cristian.adam at gmail.com (Cristian Adam) Date: Thu, 1 Jun 2017 16:48:42 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> Message-ID: > > 2. If I select the kit "Qt 5.9.0 (msvc2017-64), I get the following in > "General Messages": > > > > Running "C:\Program Files\CMake\bin\cmake.exe -E server > "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" > in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. > > The C compiler identification is unknown The CXX compiler identification > is unknown CMake Error at CMakeLists.txt:3 (project): > > No CMAKE_C_COMPILER could be found. > > > For this you need to delete / rename your Qt Creator compiler / kit configuration xml files. On Linux they are found under ~/.config/QtProject/qtcreator/, on Windows probably under %appdata% ... Cheers, Cristian. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tobias.Hunger at qt.io Thu Jun 1 16:56:24 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Thu, 1 Jun 2017 14:56:24 +0000 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com>, Message-ID: > For this you need to delete / rename your Qt Creator compiler / kit configuration xml files. Actually it should be enough to double check the compilers set up in your kit (Tools>Options>Build & Run>Kits) and maybe reset the cmake configuration for that kit. Best Regards, Tobias -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From Tobias.Hunger at qt.io Thu Jun 1 17:09:43 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Thu, 1 Jun 2017 15:09:43 +0000 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> Message-ID: > 1. Build a project mit cmake and Qt 5.8.0 (msvc2013-64) works, but I cannot debug qml (Enable QML in Debugger Settings is checked, but Application Output says: The "Enable QML in Debugger Settings will just start the debugger in Creator and try to attach to the debugging port of your application. You will need to build the support for debugging into the application for that to work though. I am no QML expert, but apparently all you need to do is to define QT_QML_DEBUG before including QtQuick. Adding that to the relevant CMake targets should work fine. Please make sure to disable QML debugging support when creating release binaries that you want to ship. Best Regards, Tobias -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From helmut.muelner at gmail.com Thu Jun 1 17:35:51 2017 From: helmut.muelner at gmail.com (=?iso-8859-1?Q?Helmut_M=FClner?=) Date: Thu, 1 Jun 2017 17:35:51 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> Message-ID: <011c01d2daec$c0733b40$4159b1c0$@gmail.com> Hi, Thanks for your help. >> 1. Build a project mit cmake and Qt 5.8.0 (msvc2013-64) works, but I cannot debug qml (Enable QML in Debugger Settings is checked, but Application Output says: >> The "Enable QML in Debugger Settings will just start the debugger in Creator and try to attach to the debugging port of your application. >>You will need to build the support for debugging into the application for that to work though. I am no QML expert, but apparently all you need to do is to define QT_QML_DEBUG before including QtQuick. Adding that to the relevant CMake targets should work fine. >> Please make sure to disable QML debugging support when creating release binaries that you want to ship. I added in my main.cpp before any include: #ifdef _DEBUG #define QT_QML_DEBUG #endif Now debugging works. Note: This is not needed if I use qmake with a project.pro file. Perhaps this should be documented in the QtCreator help. Cheers, Helmut From helmut.muelner at gmail.com Thu Jun 1 18:19:28 2017 From: helmut.muelner at gmail.com (=?utf-8?Q?Helmut_M=C3=BClner?=) Date: Thu, 1 Jun 2017 18:19:28 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> Message-ID: <015101d2daf2$d862cc60$89286520$@gmail.com> Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): No CMAKE_C_COMPILER could be found. For this you need to delete / rename your Qt Creator compiler / kit configuration xml files. On Linux they are found under ~/.config/QtProject/qtcreator/, on Windows probably under %appdata% ... On Windows these files are under %appdata%\QtProject\QtCreator I rename toolchains.xml, also removed all build-directories in my project folder – to no avail. I also rename CMakeLists.txt.user in the project folder, leading to a crash of qtcreator at the next start, but working again at the following start. I still cannot build with Qt 5.9.0 msvc2017-64. The Kits Manager show a warning : Cmake configuration has no path to a C[++] compiler set, even though the kit has a valid toolchain. I select “Microsoft Visual C++ Compilter 15.0 (amd64)” in the compiler comboboxes, and this is shown in the kit tooltip, but the problem persists. Cheers, Helmut. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias.hunger at gmail.com Thu Jun 1 20:04:37 2017 From: tobias.hunger at gmail.com (Tobias Hunger) Date: Thu, 1 Jun 2017 20:04:37 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <015101d2daf2$d862cc60$89286520$@gmail.com> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> <015101d2daf2$d862cc60$89286520$@gmail.com> Message-ID: Hi Helmut, On Jun 1, 2017 18:19, "Helmut Mülner" wrote: Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): No CMAKE_C_COMPILER could be found. Does your project contain files that need to be built with a c compiler? You might want to tell cmake not to bother checking for one if not:-) PROJECT has a way to do that. For this you need to delete / rename your Qt Creator compiler / kit configuration xml files. On Linux they are found under ~/.config/QtProject/qtcreator/, on Windows probably under %appdata% ... On Windows these files are under %appdata%\QtProject\QtCreator I rename toolchains.xml, also removed all build-directories in my project folder – to no avail. I also rename CMakeLists.txt.user in the project folder, leading to a crash of qtcreator at the next start, but working again at the following start. The stuff is in profiles.xml. Do not bother to delete that, just fix it! I still cannot build with Qt 5.9.0 msvc2017-64. The Kits Manager show a warning : Cmake configuration has no path to a C[++] compiler set, even though the kit has a valid toolchain. I select “Microsoft Visual C++ Compilter 15.0 (amd64)” in the compiler comboboxes, and this is shown in the kit tooltip, but the problem persists. Tools>Options>Build & Run>Kits, click the kits, change the cmake configuration. That is where the c comoiler/c++ compilers are defined. If you did not change those before, it should be enough to reset those to default values. Best Regards, Tobias PS: Did you upgrade Creator or is this mess with blank settings? It should leave the cmake configuration of the kits alone (I can't be sure the user has not explicitly set those!), but the compilers should have worked:-) So sorry for the mess. -------------- next part -------------- An HTML attachment was scrubbed... URL: From helmut.muelner at gmail.com Fri Jun 2 10:39:04 2017 From: helmut.muelner at gmail.com (=?utf-8?Q?Helmut_M=C3=BClner?=) Date: Fri, 2 Jun 2017 10:39:04 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> <015101d2daf2$d862cc60$89286520$@gmail.com> Message-ID: <00cd01d2db7b$b16f08b0$144d1a10$@gmail.com> On Jun 1, 2017 18:19, "Helmut Mülner" > wrote: Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): No CMAKE_C_COMPILER could be found. Does your project contain files that need to be built with a c compiler? You might want to tell cmake not to bother checking for one if not:-) PROJECT has a way to do that. This is not relevant here. The Microsoft-C-Compiler is always the same as the Microsoft-C++-Compiler. The stuff is in profiles.xml. Do not bother to delete that, just fix it! The profiles.xml looks ok as far as I can tell. In QtCreator I have the following kits: - Qt 5.8.0 (msvc2013) - Qt 5.8.0 (msvc2013-64) - Qt 5.9.0 (msvc2013-64) - Qt 5.9.0 (msvc2015( - Qt 5.9.0 (msvc2015_64) - Qt 5.9.0 (msvc2017-64) All of them except the last one work with the QtCreator cmake integration. All of them (including msvc2017-64) work with qmake. If I open a VS2017 developer console and run cmake (or cmake-gui) there I can generate a working VS2017 solution. I suspect that QtCreator does not set up the environment correctly before calling cmake. I also tried to start QtCreator from a VS2017 developer console, but this also did not work. Also tried the “x64 Native Tools Command Prompt for VS 2017” and started QtCreator from there – without success. I always get this output: Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{7fc4b436-7358-4002-8feb-2380442290e4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-bE7tFd\qtc-cmake-XXqOkacn. The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): No CMAKE_C_COMPILER could be found. Tell CMake where to find the compiler by setting either the environment variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. CMake Error at CMakeLists.txt:3 (project): No CMAKE_CXX_COMPILER could be found. Tell CMake where to find the compiler by setting either the environment variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. Configuring incomplete, errors occurred! See also "C:/Users/mue/AppData/Local/Temp/QtCreator-bE7tFd/qtc-cmake-XXqOkacn/CMakeFiles/CMakeOutput.log". See also "C:/Users/mue/AppData/Local/Temp/QtCreator-bE7tFd/qtc-cmake-XXqOkacn/CMakeFiles/CMakeError.log". If I use the “x64 Native Tools Command Prompt for VS 2017” and go to the Temp folder with the error logs, there is a subfolder “3.8.2” With two subfolders for the compiler checks. When I do “cl -c CMakeCCompilerId.c” I get the output: Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x86 Copyright (C) Microsoft Corporation. All rights reserved. CMakeCCompilerId.c And with “cl -c CMakeCXXCompilerId.cpp”: Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x86 Copyright (C) Microsoft Corporation. All rights reserved. CMakeCXXCompilerId.cpp My conclusion: QtCreator/cmake did not find the compiler. The BOOST mailing list had some discussion about problems with VS2017 some weeks ago. Some links: https://lists.boost.org/Archives/boost/2017/04/234552.php https://lists.boost.org/Archives/boost/2017/03/234024.php https://lists.boost.org/Archives/boost/2017/02/232805.php Cheers, Helmut -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eike.Ziller at qt.io Fri Jun 2 11:21:10 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Fri, 2 Jun 2017 09:21:10 +0000 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <00cd01d2db7b$b16f08b0$144d1a10$@gmail.com> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> <015101d2daf2$d862cc60$89286520$@gmail.com> <00cd01d2db7b$b16f08b0$144d1a10$@gmail.com> Message-ID: <92694DA7-3C1A-4535-BB4F-B23FA4D409FA@qt.io> Thanks for the additional information. I’m able to reproduce your issue. It looks like Qt Creator passes a wrong CMAKE_CXX_COMPILER setting in this specific case, even though the compilers are set up in the kit. When I go to "Tools > Options > Build & Run > Kits" and either remove the CMAKE_CXX_COMPILER and CMAKE_C_COMPILER entries from the “CMake Configuration”, or set them to just “cl.exe” or the absolute path to cl.exe, then configuration works for my dummy CMake based project. Br, Eike > On Jun 2, 2017, at 10:39 AM, Helmut Mülner wrote: > > On Jun 1, 2017 18:19, "Helmut Mülner" wrote: >>> Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. >>> >>> The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): >>> >>> No CMAKE_C_COMPILER could be found. >>> > Does your project contain files that need to be built with a c compiler? You might want to tell cmake not to bother checking for one if not:-) PROJECT has a way to do that. > > This is not relevant here. The Microsoft-C-Compiler is always the same as the Microsoft-C++-Compiler. > > The stuff is in profiles.xml. Do not bother to delete that, just fix it! > > The profiles.xml looks ok as far as I can tell. > > In QtCreator I have the following kits: > - Qt 5.8.0 (msvc2013) > - Qt 5.8.0 (msvc2013-64) > - Qt 5.9.0 (msvc2013-64) > - Qt 5.9.0 (msvc2015( > - Qt 5.9.0 (msvc2015_64) > - Qt 5.9.0 (msvc2017-64) > > All of them except the last one work with the QtCreator cmake integration. > All of them (including msvc2017-64) work with qmake. > > If I open a VS2017 developer console and run cmake (or cmake-gui) there I can generate a working VS2017 solution. > > I suspect that QtCreator does not set up the environment correctly before calling cmake. > I also tried to start QtCreator from a VS2017 developer console, but this also did not work. > Also tried the “x64 Native Tools Command Prompt for VS 2017” and started QtCreator from there – without success. > > I always get this output: > > Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{7fc4b436-7358-4002-8feb-2380442290e4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-bE7tFd\qtc-cmake-XXqOkacn. > The C compiler identification is unknown > The CXX compiler identification is unknown > CMake Error at CMakeLists.txt:3 (project): > No CMAKE_C_COMPILER could be found. > > Tell CMake where to find the compiler by setting either the environment > variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to > the compiler, or to the compiler name if it is in the PATH. > > > CMake Error at CMakeLists.txt:3 (project): > No CMAKE_CXX_COMPILER could be found. > > Tell CMake where to find the compiler by setting either the environment > variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path > to the compiler, or to the compiler name if it is in the PATH. > > > Configuring incomplete, errors occurred! > See also "C:/Users/mue/AppData/Local/Temp/QtCreator-bE7tFd/qtc-cmake-XXqOkacn/CMakeFiles/CMakeOutput.log". > See also "C:/Users/mue/AppData/Local/Temp/QtCreator-bE7tFd/qtc-cmake-XXqOkacn/CMakeFiles/CMakeError.log". > > If I use the “x64 Native Tools Command Prompt for VS 2017” and go to the Temp folder with the error logs, there is a subfolder “3.8.2” > With two subfolders for the compiler checks. > When I do “cl -c CMakeCCompilerId.c” I get the output: > Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x86 > Copyright (C) Microsoft Corporation. All rights reserved. > > CMakeCCompilerId.c > > > And with “cl -c CMakeCXXCompilerId.cpp”: > Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x86 > Copyright (C) Microsoft Corporation. All rights reserved. > > CMakeCXXCompilerId.cpp > > My conclusion: QtCreator/cmake did not find the compiler. > > The BOOST mailing list had some discussion about problems with VS2017 some weeks ago. > Some links: > https://lists.boost.org/Archives/boost/2017/04/234552.php > https://lists.boost.org/Archives/boost/2017/03/234024.php > https://lists.boost.org/Archives/boost/2017/02/232805.php > > Cheers, > Helmut > > > > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From Tobias.Hunger at qt.io Fri Jun 2 13:12:43 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Fri, 2 Jun 2017 11:12:43 +0000 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <92694DA7-3C1A-4535-BB4F-B23FA4D409FA@qt.io> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> <015101d2daf2$d862cc60$89286520$@gmail.com> <00cd01d2db7b$b16f08b0$144d1a10$@gmail.com>, <92694DA7-3C1A-4535-BB4F-B23FA4D409FA@qt.io> Message-ID: https://bugreports.qt.io/browse/QTCREATORBUG-18325 is the bug report for this issue. -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From helmut.muelner at gmail.com Fri Jun 2 13:14:04 2017 From: helmut.muelner at gmail.com (=?utf-8?Q?Helmut_M=C3=BClner?=) Date: Fri, 2 Jun 2017 13:14:04 +0200 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <92694DA7-3C1A-4535-BB4F-B23FA4D409FA@qt.io> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> <015101d2daf2$d862cc60$89286520$@gmail.com> <00cd01d2db7b$b16f08b0$144d1a10$@gmail.com> <92694DA7-3C1A-4535-BB4F-B23FA4D409FA@qt.io> Message-ID: <013401d2db91$58eaf620$0ac0e260$@gmail.com> Hi, this is strange: If I use the kits manager to set the compilers to I get: Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{e28feaba-544f-49ba-bfa6-5b0ee5ca1cec}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-zxPK5t\qtc-cmake-XXp2hZsu. Configuring done CMake Error: The detected version of Ninja () is less than the version of Ninja required by CMake (1.3). CMake Warning: Manually-specified variables were not used by the project: CMAKE_CXX_COMPILER CMAKE_C_COMPILER CMAKE_PREFIX_PATH QT_QMAKE_EXECUTABLE I have only one ninja.exe in the system. Ninja --version gives 1.7.2 (Also tried with 1.5.3 and 1.6.9). BR, Helmut -----Ursprüngliche Nachricht----- Von: Eike Ziller [mailto:Eike.Ziller at qt.io] Gesendet: Freitag, 2. Juni 2017 11:21 An: Helmut Mülner Cc: Tobias Hunger ; qt-creator Betreff: Re: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support Thanks for the additional information. I’m able to reproduce your issue. It looks like Qt Creator passes a wrong CMAKE_CXX_COMPILER setting in this specific case, even though the compilers are set up in the kit. When I go to "Tools > Options > Build & Run > Kits" and either remove the CMAKE_CXX_COMPILER and CMAKE_C_COMPILER entries from the “CMake Configuration”, or set them to just “cl.exe” or the absolute path to cl.exe, then configuration works for my dummy CMake based project. Br, Eike > On Jun 2, 2017, at 10:39 AM, Helmut Mülner wrote: > > On Jun 1, 2017 18:19, "Helmut Mülner" wrote: >>> Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. >>> >>> The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): >>> >>> No CMAKE_C_COMPILER could be found. >>> > Does your project contain files that need to be built with a c compiler? You might want to tell cmake not to bother checking for one if not:-) PROJECT has a way to do that. > > This is not relevant here. The Microsoft-C-Compiler is always the same as the Microsoft-C++-Compiler. > > The stuff is in profiles.xml. Do not bother to delete that, just fix it! > > The profiles.xml looks ok as far as I can tell. > > In QtCreator I have the following kits: > - Qt 5.8.0 (msvc2013) > - Qt 5.8.0 (msvc2013-64) > - Qt 5.9.0 (msvc2013-64) > - Qt 5.9.0 (msvc2015( > - Qt 5.9.0 (msvc2015_64) > - Qt 5.9.0 (msvc2017-64) > > All of them except the last one work with the QtCreator cmake integration. > All of them (including msvc2017-64) work with qmake. > > If I open a VS2017 developer console and run cmake (or cmake-gui) there I can generate a working VS2017 solution. > > I suspect that QtCreator does not set up the environment correctly before calling cmake. > I also tried to start QtCreator from a VS2017 developer console, but this also did not work. > Also tried the “x64 Native Tools Command Prompt for VS 2017” and started QtCreator from there – without success. > > I always get this output: > > Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{7fc4b436-7358-4002-8feb-2380442290e4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-bE7tFd\qtc-cmake-XXqOkacn. > The C compiler identification is unknown The CXX compiler > identification is unknown CMake Error at CMakeLists.txt:3 (project): > No CMAKE_C_COMPILER could be found. > > Tell CMake where to find the compiler by setting either the > environment variable "CC" or the CMake cache entry CMAKE_C_COMPILER to > the full path to the compiler, or to the compiler name if it is in the PATH. > > > CMake Error at CMakeLists.txt:3 (project): > No CMAKE_CXX_COMPILER could be found. > > Tell CMake where to find the compiler by setting either the > environment variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER > to the full path to the compiler, or to the compiler name if it is in the PATH. > > > Configuring incomplete, errors occurred! > See also "C:/Users/mue/AppData/Local/Temp/QtCreator-bE7tFd/qtc-cmake-XXqOkacn/CMakeFiles/CMakeOutput.log". > See also "C:/Users/mue/AppData/Local/Temp/QtCreator-bE7tFd/qtc-cmake-XXqOkacn/CMakeFiles/CMakeError.log". > > If I use the “x64 Native Tools Command Prompt for VS 2017” and go to the Temp folder with the error logs, there is a subfolder “3.8.2” > With two subfolders for the compiler checks. > When I do “cl -c CMakeCCompilerId.c” I get the output: > Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x86 > Copyright (C) Microsoft Corporation. All rights reserved. > > CMakeCCompilerId.c > > > And with “cl -c CMakeCXXCompilerId.cpp”: > Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25019 for x86 > Copyright (C) Microsoft Corporation. All rights reserved. > > CMakeCXXCompilerId.cpp > > My conclusion: QtCreator/cmake did not find the compiler. > > The BOOST mailing list had some discussion about problems with VS2017 some weeks ago. > Some links: > https://lists.boost.org/Archives/boost/2017/04/234552.php > https://lists.boost.org/Archives/boost/2017/03/234024.php > https://lists.boost.org/Archives/boost/2017/02/232805.php > > Cheers, > Helmut > > > > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From Tobias.Hunger at qt.io Fri Jun 2 13:55:50 2017 From: Tobias.Hunger at qt.io (Tobias Hunger) Date: Fri, 2 Jun 2017 11:55:50 +0000 Subject: [Qt-creator] Qt Creator 4.3.0, Qt 5.9.0: problems with cmake support In-Reply-To: <013401d2db91$58eaf620$0ac0e260$@gmail.com> References: <00f801d2dae3$625c4050$2714c0f0$@gmail.com> <015101d2daf2$d862cc60$89286520$@gmail.com> <00cd01d2db7b$b16f08b0$144d1a10$@gmail.com> <92694DA7-3C1A-4535-BB4F-B23FA4D409FA@qt.io>, <013401d2db91$58eaf620$0ac0e260$@gmail.com> Message-ID: > this is strange: > If I use the kits manager to set the compilers to I get: Please do not do that. The compiler information is needed by Qt Creator. If you want to change the information that is seen by CMake, please just edit the CMake Configuration of the Kit. There is a Change button where you can edit what is passed to all CMake invocations using that Kit. Best Regards, Tobias From jhihn at gmx.com Fri Jun 2 19:32:56 2017 From: jhihn at gmx.com (Jason H) Date: Fri, 2 Jun 2017 19:32:56 +0200 Subject: [Qt-creator] 4.4 feature req decorated scrollbars beyond code pane) Message-ID: https://bugreports.qt.io/browse/QTCREATORBUG-18333 I've talked about this on the list, but I guess I never made an issue for it before. I did search before creating it today. I'm hoping it is easy to add? From mike.jackson at bluequartz.net Fri Jun 2 20:35:46 2017 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Fri, 02 Jun 2017 14:35:46 -0400 Subject: [Qt-creator] 4.4 feature req decorated scrollbars beyond code pane) In-Reply-To: References: Message-ID: <5931B002.8020008@bluequartz.net> I would just like a scrollbar that I can actually "see". Mainly an issue with dark themes on Windows and Linux. Mike Jackson Jason H wrote: > https://bugreports.qt.io/browse/QTCREATORBUG-18333 > > I've talked about this on the list, but I guess I never made an issue for it before. I did search before creating it today. > > I'm hoping it is easy to add? > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator From jhihn at gmx.com Mon Jun 5 01:51:15 2017 From: jhihn at gmx.com (Jason H) Date: Mon, 5 Jun 2017 01:51:15 +0200 Subject: [Qt-creator] 4.4 feature req decorated scrollbars beyond code pane) In-Reply-To: <5931B002.8020008@bluequartz.net> References: <5931B002.8020008@bluequartz.net> Message-ID: Sidebar- Does anyone else experience eye strain when switching from a dark IDE (or terminal) to a light (white) browser? I actually experience pain in my eyes/head when my eyes have to adjust to the new light level. I'm not sure why dark IDEs are all the rage, but it is problematic for me. > Sent: Friday, June 02, 2017 at 2:35 PM > From: "Michael Jackson" > To: qt-creator > Subject: Re: [Qt-creator] 4.4 feature req decorated scrollbars beyond code pane) > > I would just like a scrollbar that I can actually "see". Mainly an issue > with dark themes on Windows and Linux. > > Mike Jackson > > Jason H wrote: > > https://bugreports.qt.io/browse/QTCREATORBUG-18333 > > > > I've talked about this on the list, but I guess I never made an issue for it before. I did search before creating it today. > > > > I'm hoping it is easy to add? > > > > _______________________________________________ > > Qt-creator mailing list > > Qt-creator at qt-project.org > > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > From alexander.blasche at qt.io Tue Jun 6 13:58:08 2017 From: alexander.blasche at qt.io (Alex Blasche) Date: Tue, 6 Jun 2017 11:58:08 +0000 Subject: [Qt-creator] Nominating Vikas Pachdha for Approver status In-Reply-To: References: Message-ID: Congratulations to Vikas. The rights have been adjusted. -- Alex ________________________________________ From: Development on behalf of Eike Ziller Sent: Monday, 15 May 2017 10:43:57 AM To: Cc: qt-creator Subject: [Development] Nominating Vikas Pachdha for Approver status Hereby I nominate Vikas Pachdha for Approver status. He has been defacto maintaining iOS support in Qt Creator since a year. https://codereview.qt-project.org/#/q/owner:%22Vikas+Pachdha%22+status:merged,n,z Br, -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B _______________________________________________ Development mailing list Development at qt-project.org http://lists.qt-project.org/mailman/listinfo/development From damien.courtois at gmail.com Wed Jun 7 14:09:05 2017 From: damien.courtois at gmail.com (Damien Courtois) Date: Wed, 7 Jun 2017 14:09:05 +0200 Subject: [Qt-creator] Debugging Helpers with CDB Message-ID: Hi all, Since version 4.3 of QtCreator, CDB debugging support uses the same Python backend as GDB and LLDB. It's specifically said in the release post that as such it should allow the same debugging helpers to work for GDB, LLDB and CDB. But the problem is : how do you set your extra debugging helpers in CDB ????? On Linux, in the GDB tab of the Debuggers section, I have a "Extra Debugging Helpers" entry that let me select my custom Python script, but on Windows, there is nothing in the CDB tab ... (and obviously the GDB one doesn't work for CDB) Anyone knows how to do that ? Is it possible ? Technically is should be, so my guess is that the option just hasn't been exposed in the CDB tab, but I'm not sure how to check / fix this ? Regards, Damien Courtois -------------- next part -------------- An HTML attachment was scrubbed... URL: From orgads at gmail.com Wed Jun 7 14:20:53 2017 From: orgads at gmail.com (Orgad Shaneh) Date: Wed, 7 Jun 2017 15:20:53 +0300 Subject: [Qt-creator] Debugging Helpers with CDB In-Reply-To: References: Message-ID: This is fixed in master. בתאריך 7 ביוני 2017 15:09,‏ "Damien Courtois" כתב: > Hi all, > > Since version 4.3 of QtCreator, CDB debugging support uses the same Python > backend as GDB and LLDB. It's specifically said in the release post that as > such it should allow the same debugging helpers to work for GDB, LLDB and > CDB. > But the problem is : how do you set your extra debugging helpers in CDB > ????? > On Linux, in the GDB tab of the Debuggers section, I have a "Extra > Debugging Helpers" entry that let me select my custom Python script, but on > Windows, there is nothing in the CDB tab ... (and obviously the GDB one > doesn't work for CDB) > > Anyone knows how to do that ? Is it possible ? Technically is should be, > so my guess is that the option just hasn't been exposed in the CDB tab, but > I'm not sure how to check / fix this ? > > Regards, > Damien Courtois > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From damien.courtois at gmail.com Wed Jun 7 14:26:59 2017 From: damien.courtois at gmail.com (Damien Courtois) Date: Wed, 7 Jun 2017 14:26:59 +0200 Subject: [Qt-creator] Debugging Helpers with CDB In-Reply-To: References: Message-ID: Ok, I just have to wait for the next version of Qt Creator then :) Thanks ! 2017-06-07 14:20 GMT+02:00 Orgad Shaneh : > This is fixed in master. > > בתאריך 7 ביוני 2017 15:09,‏ "Damien Courtois" > כתב: > >> Hi all, >> >> Since version 4.3 of QtCreator, CDB debugging support uses the same >> Python backend as GDB and LLDB. It's specifically said in the release post >> that as such it should allow the same debugging helpers to work for GDB, >> LLDB and CDB. >> But the problem is : how do you set your extra debugging helpers in CDB >> ????? >> On Linux, in the GDB tab of the Debuggers section, I have a "Extra >> Debugging Helpers" entry that let me select my custom Python script, but on >> Windows, there is nothing in the CDB tab ... (and obviously the GDB one >> doesn't work for CDB) >> >> Anyone knows how to do that ? Is it possible ? Technically is should be, >> so my guess is that the option just hasn't been exposed in the CDB tab, but >> I'm not sure how to check / fix this ? >> >> Regards, >> Damien Courtois >> >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjvbertin at gmail.com Thu Jun 8 15:07:09 2017 From: rjvbertin at gmail.com (=?ISO-8859-1?Q?Ren=E9_J=2EV=2E?= Bertin) Date: Thu, 08 Jun 2017 15:07:09 +0200 Subject: [Qt-creator] importing "foreign" cmake projects remains problematic Message-ID: <2261678.zHZUPy4MW1@bola> Hi, I've had another look at the current state of things in Qt Creator (v 4.3.82 aka 4.4.0 beta1), esp. CMake support. There are things that seem to have improved, enough that I am getting interested in trying out the IDE, but CMake support remains problematic enough that I can't for most of my projects. As a reminder, I maintain packaging scripts for use with a build/distribution system which requires projects to be configured through that system (MacPorts to be exhaustive; building with direct make or ninja calls is a lot more trivial once the configuration has been taken care of). I have a wrapper script that can be called instead of cmake and that ensures that the proper command is executed which will in turn execute cmake with the appropriate arguments. What's really missing from Creator is support for a separate configuration step with exact control of the arguments to be used. I also notice that Creator still calls cmake (without any control over additional arguments) even if the "automatic" option is disabled in the CMake settings panel. But that's maybe not the only glitch. I tried to import one of those MacPorts projects, configured as usual but with the "CodeBlocks - Unix Makefiles' generator under the assumption that Creator would be able to infer the project structure from that. The basic cmake (v3.8.2) call is %> cd /path/to/work/build ; cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /path/to/work/source When I import the resulting build dir in Creator I don't see the source in the IDE, but install tree. The same thing happens with CodeBlocks, btw, so this may be more a problem with Cmake's CodeBlocks generator than with Creator. I do note however that KDevelop imports the same configured project perfectly, using the compile_commands.json file that is created because of CMAKE_EXPORT_COMPILE_COMMANDS . (Not really surprising given how the intended target user of that file - the Eclipse IDE - is in a completely different league as CodeBlocks...) Cheers, René From tobias.hunger at gmail.com Thu Jun 8 21:00:28 2017 From: tobias.hunger at gmail.com (Tobias Hunger) Date: Thu, 8 Jun 2017 21:00:28 +0200 Subject: [Qt-creator] importing "foreign" cmake projects remains problematic In-Reply-To: <2261678.zHZUPy4MW1@bola> References: <2261678.zHZUPy4MW1@bola> Message-ID: Hi Rene, I probably do not fully understand what you are doing, so please be patient with me:-) On Thu, Jun 8, 2017 at 3:07 PM, René J.V. Bertin wrote: > I've had another look at the current state of things in Qt Creator (v 4.3.82 aka 4.4.0 beta1), esp. CMake support. > > There are things that seem to have improved, enough that I am getting interested in trying out the IDE, but CMake support remains problematic enough that I can't for most of my projects. Thank you for taking the time to provide your feedback instead of just running off to greener pastures! I very much appreciate the feedback on our cmake support: Without it CMake support in Creator would not be where it is today. > I have a wrapper script that can be called instead of cmake and that ensures that the proper command is executed which will in turn execute cmake with the appropriate arguments. Can you register your wrapper script with creator? That should work, provided it it (mostly) transparent and forwards the relevant arguments to the real cmake. > What's really missing from Creator is support for a separate configuration step with exact control of the arguments to be used. What do you mean here? You want the call to cmake to configure the project to be more explicit? Make/ninja are calling out to cmake all the time. Why would creator not do the same? It needs the same level of information. > I also notice that Creator still calls cmake (without any control over additional arguments) even if the "automatic" option is disabled in the CMake settings panel. Sure it does. It starts cmake and asks it for information on the project you opened directly. At least it does in server-mode. With the older tealeafreader mode it just runs cmake once to make sure the configuration is still up to date. > But that's maybe not the only glitch. I tried to import one of those MacPorts projects, configured as usual but with the "CodeBlocks - Unix Makefiles' generator under the assumption that Creator would be able to infer the project structure from that. Is one of these projects open-source? Can I open such projects on Linux for testing? I'd like to give this a whirl:-) > The basic cmake (v3.8.2) call is So you almost certainly have server-mode in your cmake:-) > %> cd /path/to/work/build ; cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /path/to/work/source I do not see why that would not work from creator. The CodeBlocks part is optional for you (your cmake has server-mode;-). So -G "Unix Makefiles" is ok. You can define the generator in the Kit. CMAKE_BUILD_TYPE=MacPorts can be configured as well. If you want to use this setting a lot, then you can set this up in the Kit as well. It has a section for CMake Configuration settings. That configuration will then be used whenever that kit is used. You can also set this via the project configuration if you do not want to see this applied so widely. You will need to manually add it there though. CMAKE_EXPORT_COMPILE_COMMANDS is not used by creator. You can still add it, with the same options as for CMAKE_BUILD_TYPE. > When I import the resulting build dir in Creator I don't see the source in the IDE, but install tree. What does that mean exactly? You do not see the files in the source directory but a list of files as they are installed? > The same thing happens with CodeBlocks, btw, so this may be more a problem with Cmake's CodeBlocks generator than with Creator. I do note however that KDevelop imports the same configured project perfectly, using the compile_commands.json file that is created because of CMAKE_EXPORT_COMPILE_COMMANDS . (Not really surprising given how the intended target user of that file - the Eclipse IDE - is in a completely different league as CodeBlocks...) I have considered using compile_commands.json file, but that would just be another hack that will fail for non-trivial projects. You get the exact compiler call for all source files from that file, but there is no context information in it, so you can not say which call belongs to which target. That is problematic when you build the same file several times -- something that happens a lot in the wild, e.g. in tests. Best Regards, Tobias From rjvbertin at gmail.com Fri Jun 9 15:43:08 2017 From: rjvbertin at gmail.com (=?ISO-8859-1?Q?Ren=E9_J=2EV=2E?= Bertin) Date: Fri, 09 Jun 2017 15:43:08 +0200 Subject: [Qt-creator] importing "foreign" cmake projects remains problematic In-Reply-To: References: <2261678.zHZUPy4MW1@bola> Message-ID: <1610222.pupye2rghe@bola> On Thursday June 08 2017 21:00:28 Tobias Hunger wrote: Hi Tobias, >I probably do not fully understand what you are doing, so please be >patient with me:-) So for the sake of clarity let me just show a few commands from a typical workflow. I already indicated that the context is MacPorts packages, its so-called ports which are manipulated using a command that's (confusingly?) called port itself. When developing them, or even when working on a software project bundled as a port (there are some advantages to that), I typically do Fetch code if not done yet, unpack, apply any local patches (port fetch, port extract, port patch) and run the configure step (showing progress): %> port -v configure foo [+build_variants] [configure.optflags=...] [configure.compiler=...] Run the build step: %> port build foo [+build_variants] Install to a local "destroot" location %> port destroot foo [+build_variants] Those could be done in a single invocation too: `port destroot foo [+build_variants] [configure.optflags=...] [configure.compiler=...]`. The steps that interest me here are the 1st two, especially the configure step itself. This is done in a special limited environment, possibly tailored for the project and with arguments to the configuration utility (e.g. cmake) that ensure a reproducable build that is exactly as it's intended to be. There's usually not a lot of need to generate very long/complex autoconf/configure command lines, contrary to cmake which tries to be too clever about too many things. It may seem contrived to want to use an IDE in combination with this kind of workflow and it's undoubtedly overkill when you just have to maintain a few "distribution patches". After all, those port commands can be seen as the commandline equivalent of their equivalent IDE features. But you can also see this as a "meta build system" that helps you formalise the whole process, making it trivial to reproduce the exact same set-up elsewhere or from scratch. And then there's of course the fact that it also allows to install and uninstall your development code much more cleanly (and in MacPorts' case, simply activate a previous, still installed version when desired). >Thank you for taking the time to provide your feedback instead of just >running off to greener pastures! My pleasure! And you know, pastures always look greener from the other side of the fence so I always keep an eye out on alternatives (though more alertly so when the grass under my feet seems to be going brown or getting thin ;)) >Can you register your wrapper script with creator? That should work, >provided it it (mostly) transparent and forwards the relevant >arguments to the real cmake. That's what I have been trying: https://github.com/RJVB/macstrop/blob/master/kf5/kdevelop5/files/cmake2port But it's important to realise that this is a very indirect wrapper to cmake, without any possibility to hand off arguments to the cmake invocation that counts. This approach almost works, and protects the build directory from unwanted or unexpected changes an inappropriate cmake command might make. But I've seen a case yesterday where all of a sudden my CMakeCache was gone, as if deleted by Creator. That's annoying because MacPorts maintains its own statefile: once a build phase like `port configure` completed successfully it is marked as done and will be skipped the next time. Then there's the fact I haven't been able to get the actual sources to show up in the project, even if it built as expected. It's a bit complicated though to get this right with Creator's concept of build kits. And I get the impression that Creator also doesn't know how to obtain a project's targets from the cmake information, and then allow building the selected target from the project tree view. >> What's really missing from Creator is support for a separate configuration step with exact control of the arguments to be used. > >What do you mean here? You want the call to cmake to configure the >project to be more explicit? Basically, yes, I miss a possibility to set up the configure step in the project configuration page. I presume you get to do this when you create a new project, but even for such projects, how do you repeat that step with the appropriate arguments? >Make/ninja are calling out to cmake all >the time. Why would creator not do the same? It needs the same level >of information. 2 reasons: make/ninja already to it (so why would Creator do it "all the time" too?). And make/ninja will raise an error in situations where running cmake (without all the appropriate arguments) will just wipe the error silently and set up things differently. Just as an example, something I'd consider a bug in cmake. CMake will get compiler options from the environment (CFLAGS & CXXFLAGS) and add them to the CMAKE_C*_FLAGS variable corresponding to your current CMAKE_BUILD_TYPE. If however you rerun cmake with a different compiler selection it will do a sort of partial reset halfway through its run, and at that point it will ignore those compiler flags. IOW, the only way I found till now to reconfigure for building with a different compiler AND use the desired compiler options is to do a `rm -rf $build.dir/CMake*` before running cmake with all necessary arguments. >It starts cmake and asks it for information on the project you opened >directly. At least it does in server-mode. With the older I already had a run-in with CMake's server mode in Kdevelop, which made me go back to a branch that doesn't use that mode. IIRC there are issues with it that won't be resolved until 3.9 . But even if it *has* to do this instead of just using the current version of the CodeBlocks project (or compile_commands.json) file maintained by cmake, it would be safer if cmake were called with all its original arguments. FWIW, KDevelop also used NOT to do that, but now does and also provides an interface to check and modify all aspects of a project's cmake invocation. >> But that's maybe not the only glitch. I tried to import one of those MacPorts projects, configured as usual but with the "CodeBlocks - Unix Makefiles' generator under the assumption that Creator would be able to infer the project structure from that. > >Is one of these projects open-source? Can I open such projects on >Linux for testing? I'd like to give this a whirl:-) They're all open source. How much time do you want to invest in whirling? You may have understood by now that doing it really in the same context will require a "certain" investment in setting things up. But it should be possible to approximate my full set-up. I used a simple KF5 Applications project for testing (KRuler), but I'd expect you should be able to use a simple Tier1 framework that doesn't have lots of additional dependencies, too. I can send you a trimmed-down script that invokes cmake directly with the really required arguments. If you invoke that to create a shadow build dir that sits next to the source dir you should get the same kind of information I have on my end and that don't import nicely. >So you almost certainly have server-mode in your cmake:-) Yes, but as evoked above, there are apparently certain issues with server mode that make it incompatible with what I'm trying to do, until v3.9 comes out. >The CodeBlocks part is optional for you (your cmake has >server-mode;-). So -G "Unix Makefiles" is ok. You can define the >generator in the Kit. Come to think of it, I have a hunch that a server mode might be incompatible with the kind of workflow described above. I'm tapping into a build system that calls on cmake but doesn't expect cmake to keep running as some sort of server instance. >It has a section for CMake Configuration settings. That configuration Yeah, I noticed. I think it could do with some helpful tooltips ;) >> When I import the resulting build dir in Creator I don't see the source in the IDE, but install tree. > >What does that mean exactly? You do not see the files in the source >directory but a list of files as they are installed? Indeed. Rather than seeing the source files, I see the /opt/local tree. Very curious. >I have considered using compile_commands.json file, but that would >just be another hack that will fail for non-trivial projects. You get >the exact compiler call for all source files from that file, but there >is no context information in it, so you can not say which call belongs >to which target. That is problematic when you build the same file >several times -- something that happens a lot in the wild, e.g. in >tests. Hmm, that might expain why KDevelop doesn't always show the build targets, and indeed there's confusion sometimes when a file belongs to multiple targets. I think though you're not entirely right: AFAIU CMake creates a subdirectory per target, and puts the object file created from source files in the that CMakeFiles/TargetName.dir directory . Isn't that enough information to infer the targets, and determine which file belongs to what target(s)? Cheers, René From rjvbertin at gmail.com Sat Jun 10 12:54:22 2017 From: rjvbertin at gmail.com (=?ISO-8859-1?Q?Ren=E9_J=2EV=2E?= Bertin) Date: Sat, 10 Jun 2017 12:54:22 +0200 Subject: [Qt-creator] importing "foreign" cmake projects remains problematic In-Reply-To: <1610222.pupye2rghe@bola> References: <2261678.zHZUPy4MW1@bola> <1610222.pupye2rghe@bola> Message-ID: <2394371.fxCEaPuU1Y@bola> To make another (more succinct) case for having a way to configure a cmake configuration step: - there are moments in the lifetime of a project you're working on where you need to reset the build. Sometimes that means discarding the whole build directory, sometimes you only need to discard the CMakeCache.txt file, and sometimes it's proven to be a good compromise to discard "CMake*" in the build.dir toplevel. - consider a project that can be built for Mac, MSWindows, X11 and why not Wayland, each with their own set of included source files and possibly build targets. In an IDE like KDevelop you can simply add a new build directory to the project and configure all aspects of the details cmake invocation - aspects which will be saved and used each time cmake needs to be run. In both cases I'd typically want to be able to get the project layout displayed appropriately in the IDE before I run a build. IOW, Creator's feature where you launch the build via `cmake --build --target ` is not exactly what I'd expect even if it probably does the job (just kill the build when it starts, right?). I've managed to support "server" mode via my cmake2port wrapper. With that I indeed get the entire project in view, including files generated in the build.dir. But there appears to be no way to specify the usual -DCMAKE_FOO arguments in that mode so I'm a bit suspicious of the whole thing. R. From ekke at ekkes-corner.org Mon Jun 12 12:43:08 2017 From: ekke at ekkes-corner.org (ekke) Date: Mon, 12 Jun 2017 12:43:08 +0200 Subject: [Qt-creator] Qt 5.8 / 5.9 iOS run gives 'Mount Developer Disk failed' Xcode 8.3.3 Message-ID: * updated from OSX 10.11.6 to 10.12.5 * updated Xcode from 8.2 to 8.3.3 * updated iOS devices from 10.2.1 to 10.3.2 now from Qt 5.8 / Creator 4.2.1 and Qt 5.9 / Creator 4.3 I can build iOS projects without a problem, but run always gives me "Mount developer disk failed" TransferAppSession(228b5d69b039befe7288041c86840326c026cdb2, /daten/_qt_sdks/sdk_590/Examples/Qt-5.9/quickcontrols2/build-gallery-iphoneos_clang_Qt_5_9_0_for_iOS-Debug/Debug-iphoneos/gallery.app)Running app "/daten/_qt_sdks/sdk_590/Examples/Qt-5.9/quickcontrols2/build-gallery-iphoneos_clang_Qt_5_9_0_for_iOS-Debug/Debug-iphoneos/gallery.app" failed. Mount developer disk failed. I can open the generated Xcode project and Run from there this works well tried again from Creator to Build and Run - but Run fails with "Mount developer disk failed" any ideas ? thanks ekke -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.croitor at qt.io Mon Jun 12 12:47:53 2017 From: alexandru.croitor at qt.io (Alexandru Croitor) Date: Mon, 12 Jun 2017 10:47:53 +0000 Subject: [Qt-creator] [Interest] Qt 5.8 / 5.9 iOS run gives 'Mount Developer Disk failed' Xcode 8.3.3 In-Reply-To: References: Message-ID: Hi, See https://bugreports.qt.io/browse/QTCREATORBUG-18380 On 12 Jun 2017, at 12:43, ekke > wrote: * updated from OSX 10.11.6 to 10.12.5 * updated Xcode from 8.2 to 8.3.3 * updated iOS devices from 10.2.1 to 10.3.2 now from Qt 5.8 / Creator 4.2.1 and Qt 5.9 / Creator 4.3 I can build iOS projects without a problem, but run always gives me "Mount developer disk failed" TransferAppSession(228b5d69b039befe7288041c86840326c026cdb2, /daten/_qt_sdks/sdk_590/Examples/Qt-5.9/quickcontrols2/build-gallery-iphoneos_clang_Qt_5_9_0_for_iOS-Debug/Debug-iphoneos/gallery.app)Running app "/daten/_qt_sdks/sdk_590/Examples/Qt-5.9/quickcontrols2/build-gallery-iphoneos_clang_Qt_5_9_0_for_iOS-Debug/Debug-iphoneos/gallery.app" failed. Mount developer disk failed. I can open the generated Xcode project and Run from there this works well tried again from Creator to Build and Run - but Run fails with "Mount developer disk failed" any ideas ? thanks ekke _______________________________________________ Interest mailing list Interest at qt-project.org http://lists.qt-project.org/mailman/listinfo/interest -------------- next part -------------- An HTML attachment was scrubbed... URL: From ekke at ekkes-corner.org Mon Jun 12 12:51:44 2017 From: ekke at ekkes-corner.org (ekke) Date: Mon, 12 Jun 2017 12:51:44 +0200 Subject: [Qt-creator] [Interest] Qt 5.8 / 5.9 iOS run gives 'Mount Developer Disk failed' Xcode 8.3.3 In-Reply-To: References: Message-ID: <52f4cffb-0b23-5d8f-74be-9072b1d172a6@ekkes-corner.org> Am 12.06.17 um 12:47 schrieb Alexandru Croitor: > Hi, > > See https://bugreports.qt.io/browse/QTCREATORBUG-18380 > > thanks thanks only did a Google search and forgot to search inside Bugreports ekke >> On 12 Jun 2017, at 12:43, ekke > > wrote: >> >> * updated from OSX 10.11.6 to 10.12.5 >> * updated Xcode from 8.2 to 8.3.3 >> * updated iOS devices from 10.2.1 to 10.3.2 >> >> now from Qt 5.8 / Creator 4.2.1 and Qt 5.9 / Creator 4.3 I can build >> iOS projects without a problem, >> >> but run always gives me "Mount developer disk failed" >> >> TransferAppSession(228b5d69b039befe7288041c86840326c026cdb2, >> /daten/_qt_sdks/sdk_590/Examples/Qt-5.9/quickcontrols2/build-gallery-iphoneos_clang_Qt_5_9_0_for_iOS-Debug/Debug-iphoneos/gallery.app)Running >> app >> "/daten/_qt_sdks/sdk_590/Examples/Qt-5.9/quickcontrols2/build-gallery-iphoneos_clang_Qt_5_9_0_for_iOS-Debug/Debug-iphoneos/gallery.app" >> failed. Mount developer disk failed. >> >> I can open the generated Xcode project and Run from there >> >> this works well >> >> tried again from Creator to Build and Run - but Run fails with "Mount >> developer disk failed" >> >> any ideas ? >> >> thanks >> >> ekke >> >> _______________________________________________ >> Interest mailing list >> Interest at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ekke at ekkes-corner.org Wed Jun 14 15:00:22 2017 From: ekke at ekkes-corner.org (ekke) Date: Wed, 14 Jun 2017 15:00:22 +0200 Subject: [Qt-creator] Qt 5.9 / QtCreator 4.3.0: Execution failed for task ':mergeDebugResources' (Android) Message-ID: sometimes after doing a fresh build of an Android project I'm getting ... Execution failed for task ':mergeDebugResources'. > Crunching Cruncher icon.png failed, see logs ... running the build again it's successful just happened again doing a first build of a project under Qt 5.9 with QtCreator 4.3.0 tried again: * clean project * delete build dir * build again - this time with success because this mergeDebugResources happens from time to time - any idea why ? thx ekke -------------- next part -------------- An HTML attachment was scrubbed... URL: From vikas.pachdha at qt.io Wed Jun 14 15:07:31 2017 From: vikas.pachdha at qt.io (Vikas Pachdha) Date: Wed, 14 Jun 2017 13:07:31 +0000 Subject: [Qt-creator] Qt 5.9 / QtCreator 4.3.0: Execution failed for task ':mergeDebugResources' (Android) In-Reply-To: References: Message-ID: Can you shorten your build path and try again? Regards, Vikas Pachdha. From: Qt-creator on behalf of ekke Organization: independent softwarearchitect Date: Wednesday, 14. June 2017 at 15:00 To: "qt-creator at qt-project.org" Subject: [Qt-creator] Qt 5.9 / QtCreator 4.3.0: Execution failed for task ':mergeDebugResources' (Android) Crunching Cruncher icon.png failed, -------------- next part -------------- An HTML attachment was scrubbed... URL: From ekke at ekkes-corner.org Wed Jun 14 15:20:16 2017 From: ekke at ekkes-corner.org (ekke) Date: Wed, 14 Jun 2017 15:20:16 +0200 Subject: [Qt-creator] Qt 5.9 / QtCreator 4.3.0: Execution failed for task ':mergeDebugResources' (Android) In-Reply-To: References: Message-ID: <9825fb19-8218-ebf2-c8c0-f78d617cf037@ekkes-corner.org> Am 14.06.17 um 15:07 schrieb Vikas Pachdha: > > Can you shorten your build path and try again? > my build path isn't so long: /daten/_qt_workspaces/work_590 plus default build directory from QtCreator - something like build-my_appname-Android_for_armeabi_v7a_GCC_4_9_Qt_5_9_0_for_Android_armv7-Debug but this error only happens from time to time. doing the same again it works. should I shorten the default build directory ? ../%{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")} ekke > > > > Regards, > > Vikas Pachdha. > > > > *From: *Qt-creator > on behalf of > ekke > *Organization: *independent softwarearchitect > *Date: *Wednesday, 14. June 2017 at 15:00 > *To: *"qt-creator at qt-project.org" > *Subject: *[Qt-creator] Qt 5.9 / QtCreator 4.3.0: Execution failed for > task ':mergeDebugResources' (Android) > > > > Crunching Cruncher icon.png failed, > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan.bennetts at gmail.com Fri Jun 16 10:31:45 2017 From: bryan.bennetts at gmail.com (Bryan Bennetts) Date: Fri, 16 Jun 2017 08:31:45 +0000 Subject: [Qt-creator] Qt Creator Clang Code Model with compile_commands.json Message-ID: Hi guys, It was suggested that I redirect my Qt Forum Question to this mailing list. Essentially I am wondering if it is feasible to get the Clang Code Model within Qt Creator reading a compile_commands.json file for its configuration. I have a monolithic project with bespoke Makefiles where varying parts of the project have different compile commands/include directives etc so the code model does not work that well, I *think* getting the above working would ameliorate this for me. Cheers, Bryan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikolai.kosjar at qt.io Fri Jun 16 14:58:20 2017 From: nikolai.kosjar at qt.io (Nikolai Kosjar) Date: Fri, 16 Jun 2017 14:58:20 +0200 Subject: [Qt-creator] Qt Creator Clang Code Model with compile_commands.json In-Reply-To: References: Message-ID: On 06/16/2017 10:31 AM, Bryan Bennetts wrote: > Hi guys, > > It was suggested that I redirect my Qt Forum Question > to > this mailing list. > > Essentially I am wondering if it is feasible to get the Clang Code Model > within Qt Creator reading a compile_commands.json file for its > configuration. While there is some libclang API to read a compilation database, we do not use it. We rely on the information from the project manager plugins (qbs, cmake, qmake, ...). Note that in the general case it's not possible to just forward the compiler flags to (lib)clang. While this might work well if your compiler is clang or gcc (since clang tries to mimic its interface), parse errors in header files might affect you one or the other way. Still, having an option to rely on compile_commands.json is certainly valuable. Please create a suggestion at https://bugreports.qt.io/ Nikolai From wpurvis at gmail.com Fri Jun 16 22:56:59 2017 From: wpurvis at gmail.com (Walter Purvis) Date: Fri, 16 Jun 2017 16:56:59 -0400 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping_?= =?utf-8?q?to_the_end?= Message-ID: Using Creator 4.3.1 on MacOS, the cursor keeps jumping to the end when I'm editing code. It happens every time I type cmd-S to save changes, but it also happens seemingly at random. It's not an infrequent occurrence, it happens *many* times in a session, and it's driving me crazy. Is there something I can do to stop it, or is this just a bug? (And is anybody else experiencing it.) -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.schulz at qt.io Mon Jun 19 07:26:04 2017 From: david.schulz at qt.io (David Schulz) Date: Mon, 19 Jun 2017 07:26:04 +0200 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: References: Message-ID: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> Hi, This doesn't sound like expected behavior, please add a report at bugreports.qt.io . Thanks David On 16-Jun-17 22:56, Walter Purvis wrote: > Is there something I can do to stop it, or is this just a bug? (And is > anybody else experiencing it.) From ekke at ekkes-corner.org Mon Jun 19 15:47:29 2017 From: ekke at ekkes-corner.org (ekke) Date: Mon, 19 Jun 2017 15:47:29 +0200 Subject: [Qt-creator] iOS release build uncount issues - implicit conversion loses integer precision Message-ID: debug build and run works well but release build I'm getting thousands of issues like this one: /daten/_qt_sdks/sdk_590/5.9/ios/include/QtCore/qvector.h:841: warning: implicit conversion loses integer precision: 'long' to 'int' [-Wshorten-64-to-32] return n - d->begin(); ~~~~~~ ~~^~~~~~~~~~~~ any idea what could be wrong ? * Qt 5.9 * Xcode 8.3.3 * iOS device 10.3.2 * macOS 10.12.5 * Creator 4.3 thx ekke -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhihn at gmx.com Mon Jun 19 18:26:44 2017 From: jhihn at gmx.com (Jason H) Date: Mon, 19 Jun 2017 18:26:44 +0200 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> Message-ID: I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. > Sent: Monday, June 19, 2017 at 1:26 AM > From: "David Schulz" > To: qt-creator at qt-project.org > Subject: Re: [Qt-creator] Editor bug – cursor keeps jumping to the end > > Hi, > > This doesn't sound like expected behavior, please add a report at > bugreports.qt.io . > > Thanks > > David From Eike.Ziller at qt.io Tue Jun 20 09:13:19 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Tue, 20 Jun 2017 07:13:19 +0000 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> Message-ID: <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> > On 19. Jun 2017, at 18:26, Jason H wrote: > > I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. That doesn’t sound like what the original poster wrote. (Cursor keeps jumping to end when editing code and every time cmd+s is used to save changes. I’m not able to reproduce this here btw, so there seems to be some specific setup leading to this.) In what way do the home/end keys do not work for you? Br, Eike > > >> Sent: Monday, June 19, 2017 at 1:26 AM >> From: "David Schulz" >> To: qt-creator at qt-project.org >> Subject: Re: [Qt-creator] Editor bug – cursor keeps jumping to the end >> >> Hi, >> >> This doesn't sound like expected behavior, please add a report at >> bugreports.qt.io . >> >> Thanks >> >> David > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From tobias.hunger at gmail.com Tue Jun 20 10:57:31 2017 From: tobias.hunger at gmail.com (Tobias Hunger) Date: Tue, 20 Jun 2017 10:57:31 +0200 Subject: [Qt-creator] importing "foreign" cmake projects remains problematic In-Reply-To: <2394371.fxCEaPuU1Y@bola> References: <2261678.zHZUPy4MW1@bola> <1610222.pupye2rghe@bola> <2394371.fxCEaPuU1Y@bola> Message-ID: Hi René, sorry, this somehow ended up in my spam folder and I only noticed your mail just now. On Sat, Jun 10, 2017 at 12:54 PM, René J.V. Bertin wrote: > To make another (more succinct) case for having a way to configure a cmake configuration step: > > - there are moments in the lifetime of a project you're working on where you need to reset the build. Sometimes that means discarding the whole build directory, sometimes you only need to discard the CMakeCache.txt file, and sometimes it's proven to be a good compromise to discard "CMake*" in the build.dir toplevel. Build > Clear CMake Configuration nukes your CMakeCache.txt file. It does auto-set the configuration you have made via creator, so that you do not have to start from scratch. Maybe that is not what you want? > - consider a project that can be built for Mac, MSWindows, X11 and why not Wayland, each with their own set of included source files and possibly build targets. In an IDE like KDevelop you can simply add a new build directory to the project and configure all aspects of the details cmake invocation - aspects which will be saved and used each time cmake needs to be run. You can set the generator and all the related things via the kit. I think that is the place where that makes the most sense. You can set generic settings you want for all projects, also via the kit. Once that has gone through you have a UI to configure the project in more details. What is missing? > In both cases I'd typically want to be able to get the project layout displayed appropriately in the IDE before I run a build. IOW, Creator's feature where you launch the build via `cmake --build --target ` is not exactly what I'd expect even if it probably does the job (just kill the build when it starts, right?). cmake --build . --target is how cmake says you should build cmake projects. Why do you think using that is a problem? It will do the right thing for all generators, so following what cmake says you should do as a developer makes creator work with all possible generator and spares it from hard-coding a mapping of cmake generators and actual build commands to call. > I've managed to support "server" mode via my cmake2port wrapper. With that I indeed get the entire project in view, including files generated in the build.dir. But there appears to be no way to specify the usual -DCMAKE_FOO arguments in that mode so I'm a bit suspicious of the whole thing. Everything you set in the kit configuration or in the project configuration will be set in server mode. No worry:-) Best Regards, Tobias From wpurvis at gmail.com Wed Jun 21 05:38:21 2017 From: wpurvis at gmail.com (Walter Purvis) Date: Tue, 20 Jun 2017 23:38:21 -0400 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> Message-ID: Bug report: https://bugreports.qt.io/browse/QTCREATORBUG-18416​ On Mon, Jun 19, 2017 at 1:26 AM, David Schulz wrote: > This doesn't sound like expected behavior, please add a report at > bugreports.qt.io . > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.jackson at bluequartz.net Wed Jun 21 05:52:24 2017 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Tue, 20 Jun 2017 23:52:24 -0400 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> Message-ID: <5949ED78.3060300@bluequartz.net> What version of macOS are you using? Which nightly of QtCreator are you using? Do you have anything like "Clean white space" on save turned on? Or something like "auto-format the file on save" turned on? -- Mike Jackson Walter Purvis wrote: > Bug report: https://bugreports.qt.io/browse/QTCREATORBUG-18416​ > > > On Mon, Jun 19, 2017 at 1:26 AM, David Schulz > wrote: > > This doesn't sound like expected behavior, please add a report at > bugreports.qt.io . > > > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator From joerg.bornemann at qt.io Thu Jun 22 10:20:01 2017 From: joerg.bornemann at qt.io (Joerg Bornemann) Date: Thu, 22 Jun 2017 10:20:01 +0200 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> Message-ID: On 20/06/2017 09:13, Eike Ziller wrote: >> On 19. Jun 2017, at 18:26, Jason H wrote: >> >> I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. [...] > In what way do the home/end keys do not work for you? I believe Jason does not expect that Home/End jumps to beginning/end of the document. That's unexpected and annoying for everyone coming from a different platform but the correct behavior for macOS. BR, Joerg From Eike.Ziller at qt.io Thu Jun 22 10:33:13 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Thu, 22 Jun 2017 08:33:13 +0000 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> Message-ID: <973B8BF0-EE5A-4E53-9FFB-15359174D4C8@qt.io> > On Jun 22, 2017, at 10:20, Joerg Bornemann wrote: > > On 20/06/2017 09:13, Eike Ziller wrote: > >>> On 19. Jun 2017, at 18:26, Jason H wrote: >>> >>> I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. > [...] >> In what way do the home/end keys do not work for you? > > I believe Jason does not expect that Home/End jumps to beginning/end of the document. That's unexpected and annoying for everyone coming from a different platform but the correct behavior for macOS. If that is the case, nowadays you can set different shortcuts for these in Qt Creator in Environment > Keyboard, TextEditor / GotoLineStart and GotoLineEnd. Br, -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From jhihn at gmx.com Fri Jun 23 16:44:16 2017 From: jhihn at gmx.com (Jason H) Date: Fri, 23 Jun 2017 16:44:16 +0200 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> Message-ID: Well, except that I've been using QtCreator on OSX for 3+ years. What has changed is I traded my mac mini in for a MacBook, so there is a chance that it is a config issue. However think I would remember. And **however, it's only doing it in QtCreator.** Chrome, Komodo all go to EOL on end, BOL on home. The anomaly here is QtC. > Sent: Thursday, June 22, 2017 at 4:20 AM > From: "Joerg Bornemann" > To: "Eike Ziller" , "Jason H" > Cc: "qt-creator at qt-project.org" > Subject: Re: [Qt-creator] Editor bug – cursor keeps jumping to the end > > On 20/06/2017 09:13, Eike Ziller wrote: > > >> On 19. Jun 2017, at 18:26, Jason H wrote: > >> > >> I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. > [...] > > In what way do the home/end keys do not work for you? > > I believe Jason does not expect that Home/End jumps to beginning/end of > the document. That's unexpected and annoying for everyone coming from a > different platform but the correct behavior for macOS. > > > BR, > > Joerg > From jhihn at gmx.com Fri Jun 23 16:53:50 2017 From: jhihn at gmx.com (Jason H) Date: Fri, 23 Jun 2017 16:53:50 +0200 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: <973B8BF0-EE5A-4E53-9FFB-15359174D4C8@qt.io> References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> <973B8BF0-EE5A-4E53-9FFB-15359174D4C8@qt.io> Message-ID: 1. I'm glad I can re-map it. 2. But why don't they do what everything (Chrome, Komodo, Word) else does?* * Since it's been brought up, TextEdit, Safari is doing the BOD, EOD. It seems that only Apple apps use the document navigation? > Sent: Thursday, June 22, 2017 at 4:33 AM > From: "Eike Ziller" > To: "Joerg Bornemann" > Cc: "Jason H" , "qt-creator at qt-project.org" > Subject: Re: [Qt-creator] Editor bug – cursor keeps jumping to the end > > > > On Jun 22, 2017, at 10:20, Joerg Bornemann wrote: > > > > On 20/06/2017 09:13, Eike Ziller wrote: > > > >>> On 19. Jun 2017, at 18:26, Jason H wrote: > >>> > >>> I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. > > [...] > >> In what way do the home/end keys do not work for you? > > > > I believe Jason does not expect that Home/End jumps to beginning/end of the document. That's unexpected and annoying for everyone coming from a different platform but the correct behavior for macOS. > > If that is the case, nowadays you can set different shortcuts for these in Qt Creator in Environment > Keyboard, TextEditor / GotoLineStart and GotoLineEnd. > > Br, > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Rudower Chaussee 13 > D-12489 Berlin > eike.ziller at qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B > > From Eike.Ziller at qt.io Mon Jun 26 09:58:29 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Mon, 26 Jun 2017 07:58:29 +0000 Subject: [Qt-creator] =?utf-8?q?Editor_bug_=E2=80=93_cursor_keeps_jumping?= =?utf-8?q?_to_the_end?= In-Reply-To: References: <409d5bcd-f647-a63d-a54a-46106b3a4dcf@qt.io> <0CCBD07B-3111-4983-AB77-FC0A079A64FD@qt.io> <973B8BF0-EE5A-4E53-9FFB-15359174D4C8@qt.io> Message-ID: > On 23. Jun 2017, at 16:53, Jason H wrote: > > 1. I'm glad I can re-map it. > 2. But why don't they do what everything (Chrome, Komodo, Word) else does?* Because the Apps you quote obviously chose to ignore UI guidelines. > * Since it's been brought up, TextEdit, Safari is doing the BOD, EOD. It seems that only Apple apps use the document navigation? Native macOS application do it, not only from Apple. Br, Eike > Sent: Thursday, June 22, 2017 at 4:33 AM >> From: "Eike Ziller" >> To: "Joerg Bornemann" >> Cc: "Jason H" , "qt-creator at qt-project.org" >> Subject: Re: [Qt-creator] Editor bug – cursor keeps jumping to the end >> >> >>> On Jun 22, 2017, at 10:20, Joerg Bornemann wrote: >>> >>> On 20/06/2017 09:13, Eike Ziller wrote: >>> >>>>> On 19. Jun 2017, at 18:26, Jason H wrote: >>>>> >>>>> I thought it was just me, but I'm seeing this too. using the cmd-arrow keys works as expected, it's just the home/end keys for me. >>> [...] >>>> In what way do the home/end keys do not work for you? >>> >>> I believe Jason does not expect that Home/End jumps to beginning/end of the document. That's unexpected and annoying for everyone coming from a different platform but the correct behavior for macOS. >> >> If that is the case, nowadays you can set different shortcuts for these in Qt Creator in Environment > Keyboard, TextEditor / GotoLineStart and GotoLineEnd. >> >> Br, >> -- >> Eike Ziller >> Principal Software Engineer >> >> The Qt Company GmbH >> Rudower Chaussee 13 >> D-12489 Berlin >> eike.ziller at qt.io >> http://qt.io >> Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho >> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B >> >> -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From ernst.maurer at gmail.com Mon Jun 26 20:34:38 2017 From: ernst.maurer at gmail.com (Ernst Maurer) Date: Mon, 26 Jun 2017 18:34:38 +0000 Subject: [Qt-creator] Debugger Log Message-ID: hi need a little assistance, please advise: direct GDB commands are preferable for me in some cases rather than GUI tool windows. the only problem - I can't find a short cut to switch a focus to this window and release this back. Does anyone know how to do this and is this possible at all? Rgds, Ernst -------------- next part -------------- An HTML attachment was scrubbed... URL: From asmaloney at gmail.com Mon Jun 26 21:34:41 2017 From: asmaloney at gmail.com (Andy) Date: Mon, 26 Jun 2017 21:34:41 +0200 Subject: [Qt-creator] QtC 4.3 on macOS 10.12.5 Message-ID: I had to get one of those "new" Macs with the touch bar thingy as an emergency replacement for an older Pro. I just fired up a project to work on it with Creator 4.3 and have run into a couple of problems that seem to be related to the code model. 1) F4 isn't switching properly between header and source (though F2 to Follow Symbol works) 2) "Find Usages" doesn't find them all - only in the source & header, not the rest of the project I have "Clang Code Model" active in the plugins but it doesn't seem to make a difference if it's on or not. This project is over a decade old, so I don't think it's anything I've done to it... Any suggestions? It makes it almost unusable for me because I use those two features heavily. Is there some other setting I'm missing somewhere? Thanks! --- Andy Maloney // https://asmaloney.com twitter ~ @asmaloney -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikolai.kosjar at qt.io Tue Jun 27 08:40:12 2017 From: nikolai.kosjar at qt.io (Nikolai Kosjar) Date: Tue, 27 Jun 2017 08:40:12 +0200 Subject: [Qt-creator] QtC 4.3 on macOS 10.12.5 In-Reply-To: References: Message-ID: On 06/26/2017 09:34 PM, Andy wrote: > I had to get one of those "new" Macs with the touch bar thingy as an > emergency replacement for an older Pro. > > I just fired up a project to work on it with Creator 4.3 and have run > into a couple of problems that seem to be related to the code model. > > 1) F4 isn't switching properly between header and source (though F2 to > Follow Symbol works) > 2) "Find Usages" doesn't find them all - only in the source & header, > not the rest of the project > > I have "Clang Code Model" active in the plugins but it doesn't seem to > make a difference if it's on or not. > > This project is over a decade old, so I don't think it's anything I've > done to it... > > Any suggestions? It makes it almost unusable for me because I use those > two features heavily. Is there some other setting I'm missing somewhere? > > Thanks! Which type of project is this? Does it work with a mini project of the same type? So your operating system changed. I'm wondering if this could be related to the file system (settings). Was your project indexed? When opening the project, you should see a "Parsing C/C++ Files" progress bar (might be collapsed) on the bottom right. You could also check the indexed files: Menu:Tools>C++>"Inspect C++ Code Model..." - in the "Snapshot and Documents" tab, choose "Global/Indexing Snapshot" and check whether the typical files you are working with are there. If that looks good, please create a report at https://bugreports.qt.io/ with a minimal project to reproduce. Nikolai From asmaloney at gmail.com Tue Jun 27 10:12:13 2017 From: asmaloney at gmail.com (Andy) Date: Tue, 27 Jun 2017 10:12:13 +0200 Subject: [Qt-creator] QtC 4.3 on macOS 10.12.5 In-Reply-To: References: Message-ID: Thanks Nikolai. This is a C++/qmake project. I just tried it this morning - it looks like it indexed when I opened it and it is working. Yesterday I restarted several times and it refused to work. Thanks for pointing the indexing info out - I didn't know that was there. Is there a way to completely re-index a project if I need to in the future? I don't know what's going on, but since I'm in Copenhagen I'll blame Loki. --- Andy Maloney // https://asmaloney.com twitter ~ @asmaloney On Tue, Jun 27, 2017 at 8:40 AM, Nikolai Kosjar wrote: > On 06/26/2017 09:34 PM, Andy wrote: > >> I had to get one of those "new" Macs with the touch bar thingy as an >> emergency replacement for an older Pro. >> >> I just fired up a project to work on it with Creator 4.3 and have run >> into a couple of problems that seem to be related to the code model. >> >> 1) F4 isn't switching properly between header and source (though F2 to >> Follow Symbol works) >> 2) "Find Usages" doesn't find them all - only in the source & header, >> not the rest of the project >> >> I have "Clang Code Model" active in the plugins but it doesn't seem to >> make a difference if it's on or not. >> >> This project is over a decade old, so I don't think it's anything I've >> done to it... >> >> Any suggestions? It makes it almost unusable for me because I use those >> two features heavily. Is there some other setting I'm missing somewhere? >> >> Thanks! >> > > Which type of project is this? Does it work with a mini project of the > same type? > > So your operating system changed. I'm wondering if this could be related > to the file system (settings). > > Was your project indexed? When opening the project, you should see a > "Parsing C/C++ Files" progress bar (might be collapsed) on the bottom > right. You could also check the indexed files: Menu:Tools>C++>"Inspect C++ > Code Model..." - in the "Snapshot and Documents" tab, choose > "Global/Indexing Snapshot" and check whether the typical files you are > working with are there. > > If that looks good, please create a report at https://bugreports.qt.io/ > with a minimal project to reproduce. > > Nikolai > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikolai.kosjar at qt.io Tue Jun 27 10:18:15 2017 From: nikolai.kosjar at qt.io (Nikolai Kosjar) Date: Tue, 27 Jun 2017 10:18:15 +0200 Subject: [Qt-creator] QtC 4.3 on macOS 10.12.5 In-Reply-To: References: Message-ID: On 06/27/2017 10:12 AM, Andy wrote: > Thanks for pointing the indexing info out - I didn't know that was > there. Is there a way to completely re-index a project if I need to in > the future? If you close and re-open the project, it will be re-indexed again. Nikolai From Eike.Ziller at qt.io Wed Jun 28 11:24:44 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Wed, 28 Jun 2017 09:24:44 +0000 Subject: [Qt-creator] Dev: Qt Creator 4.4 branch created Message-ID: <065A3767-3303-4867-97A2-CA140A9010A7@qt.io> In preparation for the feature freeze of Qt Creator 4.4 (*), I’ve created the 4.4 branch from master. Please start targeting the 4.4 branch instead of master. A final merge from master to 4.4 will be done next week after the feature freeze, so your open changes for master that you submit until then will also automatically end up in 4.4. Br, Eike (*) https://wiki.qt.io/Qt_Creator_Releases -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From Helmut.Muelner at nextsense.at Thu Jun 1 16:27:59 2017 From: Helmut.Muelner at nextsense.at (=?utf-8?B?SGVsbXV0IE3DvGxuZXI=?=) Date: Thu, 01 Jun 2017 14:27:59 -0000 Subject: [Qt-creator] Qt Creator 4.3.0 and Qt-5.9.0: problems with integrated cmake support Message-ID: <021681eb51bc43f289833e96eeaae223@nextsense.at> Hi, I have two problems: 1. Build a project mit cmake and Qt 5.8.0 (msvc2013-64) works, but I cannot debug qml (Enable QML in Debugger Settings is checked, but Application Output says: QML Debugger: Ignoring "-qmljsdebugger=port:64821,block,services:DebugMessages,QmlDebugger,V8Debugger,QmlInspector". Debugging has not been enabled. 2. If I select the kit "Qt 5.9.0 (msvc2017-64), I get the following in "General Messages": Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. The C compiler identification is unknown The CXX compiler identification is unknown CMake Error at CMakeLists.txt:3 (project): No CMAKE_C_COMPILER could be found. Can anybody tell me what to do? Cheers Helmut Helmut MÜLNER Software Development Engineer NEXTSENSE GmbH Straßganger Straße 295, 8053 Graz, AUSTRIA Tel. +43 664 9146112, Mobil +43 664 9146112 Fax +43 316 232 400 - 599 Mail helmut.muelner at nextsense.at, www.nextsense.at Com. Reg. Court: District Court for Civil Law Cases, Graz Com. Reg. No.: FN 288779a, VAT No.: ATU63254329 From basu.aveek at gmail.com Fri Jun 9 17:19:42 2017 From: basu.aveek at gmail.com (Aveek Basu) Date: Fri, 09 Jun 2017 15:19:42 -0000 Subject: [Qt-creator] QT expert's help required for mentoring Linux Foundation GSoC project. Message-ID: Hi, This is Aveek from Linux Foundation. Currently myself and Till Kempeter, are working as the org admins of the LF GSoC project. This year have undertaken a project of developing the Common Print Dialog for Linux ( https://wiki.linuxfoundation.org/gsoc/google-summer-code-20 17-openprinting-projects). This project will for sure improve the user experience on how we all print in Linux today. The project involves development of the complex Common Print dialogs in QT. We are badly in need of someone who has development experience in QT upstream to guide our students. It will be of great help if someone from the community could could show interest. Thanks in advance. Regards, Aveek Org Admin The Linux Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andre.Poenitz at qt.io Tue Jun 27 13:01:02 2017 From: Andre.Poenitz at qt.io (Andre Poenitz) Date: Tue, 27 Jun 2017 11:01:02 +0000 Subject: [Qt-creator] Debugger Log In-Reply-To: References: Message-ID: Ernst Maurer wrote: > need a little assistance, please advise: > direct GDB commands are preferable for me in some cases > rather than GUI tool windows. the only problem - I can't find a > short cut to switch a focus to this window and release this back. > Does anyone know how to do this and is this possible at all? I am afraid it isn't. The quickest way is with the mouse to right-click on the header of any debugger tool view (or left-click on the 'Views' item in the debugger toolbar), and left-click on the '[ ] Debugger Log' item. With the keyboard it'd be something like Alt-W, V, 7x, , which, I guess, does not really count. Out of curiosity: Which direct GDB commands do you use? Andre' From orgads at gmail.com Wed Jun 28 11:47:45 2017 From: orgads at gmail.com (Orgad Shaneh) Date: Wed, 28 Jun 2017 12:47:45 +0300 Subject: [Qt-creator] Debugger Log In-Reply-To: References: Message-ID: On Tue, Jun 27, 2017 at 2:01 PM, Andre Poenitz wrote: > Ernst Maurer wrote: >> need a little assistance, please advise: >> direct GDB commands are preferable for me in some cases >> rather than GUI tool windows. the only problem - I can't find a >> short cut to switch a focus to this window and release this back. >> Does anyone know how to do this and is this possible at all? > > I am afraid it isn't. > > The quickest way is with the mouse to right-click on the header > of any debugger tool view (or left-click on the 'Views' item in the > debugger toolbar), and left-click on the '[ ] Debugger Log' item. > > With the keyboard it'd be something like Alt-W, V, 7x, > , which, I guess, does not really count. You can assign a shortcut by Tools -> Options -> Environment -> Keyboard -> Debugger.Docks.OutputDockWidget Notice that you have to switch to debug mode for this option to appear (discovered it just now :)). - Orgad From Eike.Ziller at qt.io Wed Jun 28 11:52:18 2017 From: Eike.Ziller at qt.io (Eike Ziller) Date: Wed, 28 Jun 2017 09:52:18 +0000 Subject: [Qt-creator] Qt Creator 4.3.0 and Qt-5.9.0: problems with integrated cmake support In-Reply-To: <021681eb51bc43f289833e96eeaae223@nextsense.at> References: <021681eb51bc43f289833e96eeaae223@nextsense.at> Message-ID: <7A5757F3-E6E3-4CDA-B7B7-BBCC552AF4C6@qt.io> > On 1. Jun 2017, at 16:26, Helmut Mülner wrote: > > Hi, > > I have two problems: > > 1. Build a project mit cmake and Qt 5.8.0 (msvc2013-64) works, but I cannot debug qml (Enable QML in Debugger Settings is checked, but Application Output says: > QML Debugger: Ignoring "-qmljsdebugger=port:64821,block,services:DebugMessages,QmlDebugger,V8Debugger,QmlInspector". Debugging has not been enabled. > > 2. If I select the kit "Qt 5.9.0 (msvc2017-64), I get the following in "General Messages": > > Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{cdb7ec38-096b-4a3d-9b84-fc91923889d4}" --experimental" in C:\Users\mue\AppData\Local\Temp\QtCreator-P1XkOA\qtc-cmake-XXF8mA7w. > The C compiler identification is unknown > The CXX compiler identification is unknown > CMake Error at CMakeLists.txt:3 (project): > No CMAKE_C_COMPILER could be found. Sounds like https://bugreports.qt.io/browse/QTCREATORBUG-17925 Br, Eike > > Can anybody tell me what to do? > > Cheers > Helmut > > > > > > Helmut MÜLNER > Software Development Engineer > > NEXTSENSE GmbH > Straßganger Straße 295, 8053 Graz, AUSTRIA > Tel. +43 664 9146112, Mobil +43 664 9146112 > Fax +43 316 232 400 - 599 > Mail helmut.muelner at nextsense.at, www.nextsense.at > Com. Reg. Court: District Court for Civil Law Cases, Graz > Com. Reg. No.: FN 288779a, VAT No.: ATU63254329 > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.ziller at qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B From ernst.maurer at gmail.com Wed Jun 28 16:48:13 2017 From: ernst.maurer at gmail.com (Ernst Maurer) Date: Wed, 28 Jun 2017 14:48:13 +0000 Subject: [Qt-creator] Debugger Log In-Reply-To: References: Message-ID: it really works. thank you. unfortunately it only shows Debugger Log widget but doesn't focus on command console. the idea was to switch from e.g. step-by-step tracing to GDB commands, perform some command and switch back On Wed, Jun 28, 2017 at 12:47 PM Orgad Shaneh wrote: > On Tue, Jun 27, 2017 at 2:01 PM, Andre Poenitz > wrote: > > Ernst Maurer wrote: > >> need a little assistance, please advise: > >> direct GDB commands are preferable for me in some cases > >> rather than GUI tool windows. the only problem - I can't find a > >> short cut to switch a focus to this window and release this back. > >> Does anyone know how to do this and is this possible at all? > > > > I am afraid it isn't. > > > > The quickest way is with the mouse to right-click on the header > > of any debugger tool view (or left-click on the 'Views' item in the > > debugger toolbar), and left-click on the '[ ] Debugger Log' item. > > > > With the keyboard it'd be something like Alt-W, V, 7x, > > , which, I guess, does not really count. > > You can assign a shortcut by Tools -> Options -> Environment -> > Keyboard -> Debugger.Docks.OutputDockWidget > > Notice that you have to switch to debug mode for this option to appear > (discovered it just now :)). > > - Orgad > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ernst.maurer at gmail.com Wed Jun 28 16:50:45 2017 From: ernst.maurer at gmail.com (Ernst Maurer) Date: Wed, 28 Jun 2017 14:50:45 +0000 Subject: [Qt-creator] Debugger Log In-Reply-To: References: Message-ID: I was a little bit wrong - one more shortcut - back tab (Shift+Tab) bring the command console in to the focus. it's not an ideal but better than nothing On Wed, Jun 28, 2017 at 5:48 PM Ernst Maurer wrote: > it really works. thank you. > > unfortunately it only shows Debugger Log widget but doesn't focus on > command console. > the idea was to switch from e.g. step-by-step tracing to GDB commands, > perform some command and switch back > > > On Wed, Jun 28, 2017 at 12:47 PM Orgad Shaneh wrote: > >> On Tue, Jun 27, 2017 at 2:01 PM, Andre Poenitz >> wrote: >> > Ernst Maurer wrote: >> >> need a little assistance, please advise: >> >> direct GDB commands are preferable for me in some cases >> >> rather than GUI tool windows. the only problem - I can't find a >> >> short cut to switch a focus to this window and release this back. >> >> Does anyone know how to do this and is this possible at all? >> > >> > I am afraid it isn't. >> > >> > The quickest way is with the mouse to right-click on the header >> > of any debugger tool view (or left-click on the 'Views' item in the >> > debugger toolbar), and left-click on the '[ ] Debugger Log' item. >> > >> > With the keyboard it'd be something like Alt-W, V, 7x, >> > , which, I guess, does not really count. >> >> You can assign a shortcut by Tools -> Options -> Environment -> >> Keyboard -> Debugger.Docks.OutputDockWidget >> >> Notice that you have to switch to debug mode for this option to appear >> (discovered it just now :)). >> >> - Orgad >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/qt-creator >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.page3 at baesystems.com Thu Jun 29 21:14:32 2017 From: andy.page3 at baesystems.com (Page, Andy (UK)) Date: Thu, 29 Jun 2017 19:14:32 +0000 Subject: [Qt-creator] QTCreator + CMAKE Project View. Message-ID: <01D6881EC012F84CB4B5A83A0989E73D015D2235D0@GLKXM0002V.GREENLNK.net> I can't believe I am the only person to have queried this behaviour. When I run CMAKE from QTCREATOR - I don't see source files associated with individual CMAKE targets(libraries / exes) rather I see all source files. i.e. I don't necessarily see which files go with which targets, and more than that some files go with many different targets with possible different configuration parameters. i.e. the typical project layout I would expect from visual studio. Is it possible to switch to this view ( and I have missed the obvious). QTCREATOR knows which CMAKE targets are present, and I am pretty certain that the CODEBLOCKS project file that is generated by QTCREATOR as the intermediate format it uses, also has which files belong to which target. Can some expert tell what I am missing !!! ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.jackson at bluequartz.net Thu Jun 29 22:25:16 2017 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Thu, 29 Jun 2017 16:25:16 -0400 Subject: [Qt-creator] QTCreator + CMAKE Project View. In-Reply-To: <01D6881EC012F84CB4B5A83A0989E73D015D2235D0@GLKXM0002V.GREENLNK.net> References: <01D6881EC012F84CB4B5A83A0989E73D015D2235D0@GLKXM0002V.GREENLNK.net> Message-ID: <5955622C.605@bluequartz.net> which version of QtCreator and what version of CMake? -- Mike Jackson [mike.jackson at bluequartz.net] Page, Andy (UK) wrote: > I can’t believe I am the only person to have queried this behaviour. > > When I run CMAKE from QTCREATOR - I don't see source files associated > with individual CMAKE targets(libraries / exes) rather I see all source > files. > i.e. I don't necessarily see which files go with which targets, and more > than that some files go with many different targets with possible > different configuration parameters. > *i.e. the typical project layout I would expect from visual studio.* > > Is it possible to switch to this view ( and I have missed the obvious). > > QTCREATOR knows which CMAKE targets are present, and I am pretty certain > that the CODEBLOCKS project file that is generated by QTCREATOR as the > intermediate format it uses, also has which files belong to which target. > > Can some expert tell what I am missing !!! > > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > > _______________________________________________ > Qt-creator mailing list > Qt-creator at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator