Qt Creator and other tools

@fem_dev said in Build with mingw32-make *very* slow: First Question Qt Creator starts to use jom, but I got this compile time errors: 09:35:09: The process "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" exited normally. 09:35:09: Starting: "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" -j4 jom 1.1.3 - empower your colors cd App / && (test -e Makefile || C: /Qt/5.15.0/mingw81_64/bin/qmake.exe -o Makefile C: /Users/VM/Desktop/rotortest/App/App.pro -spec win32- g ++ CONFIG + = debug CONFIG + = qml_debug) && C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe -f Makefile C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe -f Makefile.Debug 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/app.ui -o ui_app.h The syntax of the file name, directory name, or volume label is incorrect. jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_app.h] Error 1 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/custom_widget/value_unit.ui -o ui_value_unit.h 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/form/form_assembly.ui -o ui_form_assembly.h 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/form/form_excitation.ui -o ui_form_excitation.h The syntax of the file name, directory name, or volume label is incorrect. The syntax of the file name, directory name, or volume label is incorrect. jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_form_assembly.h] Error 1 jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_value_unit.h] Error 1 The syntax of the file name, directory name, or volume label is incorrect. jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_form_excitation.h] Error 1 jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile [debug] Error 2 jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ Makefile [sub-App-make_first] Error 2 09:35:10: The process "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" exited with code 2. Error while building / deploying project rotortest (kit: Desktop Qt 5.15.0 MinGW 64-bit) When executing step "Make" How can I fix it? My system: Qt Creator 4.12.4 (GCC based - downloaded by MSYS2) Qt 5.15.0 Windows 10 x64 Mingw-w64 jom Should be completely irrelevant. When your make file works with mingw-make, it has to work with jom as well. jomis a replacement for nmake because it did not allow -j parameter. AFAIK the MSVC does support directly multi-threading and it is not done through nmake. Besides possible side effects through parallel access to the same file or whatever, there is no difference for compilation. You are listing compile errors which are due to the compiler you are using. Second question @koahnig said in Build with mingw32-make *very* slow: Mingw-make does support now multi-threading. I did some tests back then, but after a reinstall, there was no need anymore. Are you saying that you compiled your Qt project using the default MSYS2 Mingw-64 configuration (WITHOUT jom) and got a close time compilation speed compared with MSVC 2019? Nope. I do not use MSVC 2019 compiler at all. AFAIK there was an issue with an older MinGW-make not suporting multi-threading. Therefore this discussion and the solution with jom. After my reinstall I did not bother to set up jom again. At day's end some gain is possible by switching to jom, but it was not enough to go through the hassle again. You seem to use a self-compiled Qt creator version. The output shows strange blanks around the backslashes. Possibly there is your problem with compilation.

Yes, problem solved. I'm a bit ashamed that it was so simple and I tried so hard and didn't get it. Thank you very much SGaist!

@SkyHawk said in QTCreator crashes on start with segmentation fault: 4.11.0 It's an oldie. Consider updating, maybe the crash has already been fixed.

Also encountered this very same problem. It's definitely a GDB bug. It even happens when I compile a simple C++ hello world program from the console and then debug it with gdb. As soon as you hit a breakpoint and ask the debugger "info registers" then it's all over. Have created a ticket here: https://sourceware.org/bugzilla/show_bug.cgi?id=26304

Check out https://stackoverflow.com/questions/1356328/console-input-with-qt-creator You can set it in Qt Creator->Options : Environment : System : Terminal

Thanks, that fixed it.

@SGaist : Thanks again, it worked by putting all the code into the header file. I could not figure out which way would be more "correct".

Go to Projects->Build. Then check "Advanced" under CMake. Then check value of CMAKE_VERBOSE_MAKEFILE to so that it becomes TRUE.

@mzimmers said in possible to copy a kit from one PC to another?: OK, but...tarball what exactly? Tarball your Qt libraries for that kit. And tarball your cross-compiler if the other machine doesn't have it. I only want to copy one of my kits, and it would be nice it I didn't have to go back into Creator and manually update all the settings for that kit. I've never tried to export kit settings from Qt Creator, but the sdktool might do what you want. It comes bundled with Qt Creator, and it's what the official installer uses to register kits: https://github.com/qt-creator/qt-creator/blob/master/src/tools/sdktool/README.md If this is a once-off though, it might be faster to manually update the settings in your new PC.

I downloaded It from arch extra/qtcreator archlinux.org/packages/extra/x86_64/qtcreator qtcreator -version Qt Creator 4.12.4 based on Qt 5.15.0 Android 4.12.4 Support for deployment to and execution on Android Devices. AutoTest 4.12.4 Auto Test plugin. AutotoolsProjectManager 4.12.4 Autotools project integration. BareMetal 4.12.4 This plugin adds a target for bare metal development. Bazaar 4.12.4 Bazaar integration. Beautifier 4.12.4 Format source files with the help of beautifiers like AStyle, uncrustify or clang-format. BinEditor 4.12.4 Binary editor component. Bookmarks 4.12.4 Bookmarks in text editors. Boot2Qt 4.12.4 Support for the Boot2Qt Device access using the Qt Debug Bridge. CMakeProjectManager 4.12.4 CMake support. CVS 4.12.4 CVS integration. ClangCodeModel 4.12.4 Clang Code Model plugin. ClangFormat 4.12.4 clang-format indentation plugin. ClangPchManager 4.12.4 Clang precompiled header plugin. ClangRefactoring 4.12.4 Clang Refactoring plugin. ClangTools 4.12.4 ClangTools Plugin. ClassView 4.12.4 Class View component. ClearCase 4.12.4 ClearCase integration. CodePaster 4.12.4 Codepaster plugin for pushing/fetching diff from server. CompilationDatabaseProjectManager 4.12.4 Compilation Database project support. Core 4.12.4 The core plugin for the Qt IDE. CppEditor 4.12.4 C/C++ editor component. CppTools 4.12.4 Tools for analyzing C/C++ code. Cppcheck 4.12.4 Cppcheck static analyzer tool integration. See http://cppcheck.sourceforge.net. CtfVisualizer 4.12.4 Chrome Trace Format Visualizer Plugin. Debugger 4.12.4 Debugger integration. Designer 4.12.4 Qt Designer integration. DiffEditor 4.12.4 Diff editor component. EmacsKeys 4.12.4 The main idea behind this plugin is to provide additional actions a typical emacs user would expect. It doesn't claim to provide full emacs emulation. The following actions are available: - Movement [C-f, C-b, C-n, C-p, M-f, M-b, C-a, C-e, M-<, M->] - Mark-based selection [C-SPC, C-x C-x] - Cut/copy/yank (doesn't provide kill ring feature) [M-w, C-w, C-y] - Kill actions, which interact properly with clipboard [C-k, M-d, C-d] - Scrolling (half of the screen, keeps cursor visible) [C-v, M-v] - Insert new line and indent [C-j] IMPORTANT: Actions are not bound to any key combinations by default. You can find them under 'EmacsKeys' section in keyboard shortcuts settings. Also it's worth mentioning that EmacsKeys plugin forces disabling of menu mnemonics by calling Qt's qt_set_sequence_auto_mnemonic function with false argument. Many of the english menu mnemonics get into the way of typical emacs keys, this includes: Alt+F (File), Alt+B (Build), Alt+W (Window). It's a temporary solution, it remains until there is a better one. FakeVim 4.12.4 VI-style keyboard navigation. GLSLEditor 4.12.4 Editor for GLSL. GenericProjectManager 4.12.4 Generic support. Git 4.12.4 Git integration. HelloWorld 4.12.4 Hello World sample plugin. Help 4.12.4 Help system. ImageViewer 4.12.4 Image Viewer component. Ios 4.12.4 Support for deployment to and execution on iOS Devices. LanguageClient 4.12.4 Language Server Protocol client component. See https://microsoft.github.io/language-server-protocol/overview for an overview on Language Servers. Macros 4.12.4 Macros in text editors. Marketplace 4.12.4 Qt Marketplace plugin. McuSupport 4.12.4 Helper for MCU related projects. Mercurial 4.12.4 Mercurial integration. ModelEditor 4.12.4 Graphical modeling with structured diagrams. Nim 4.12.4 Plugin for supporting the Nim programming language. PerfProfiler 4.12.4 Perf Profiler Plugin. Perforce 4.12.4 Perforce integration. ProjectExplorer 4.12.4 ProjectExplorer framework that can be extended with different kind of project types. Python 4.12.4 Plugin for supporting the Python language. QbsProjectManager 4.12.4 QBS support. QmakeProjectManager 4.12.4 Provides project type for Qt/QMake .pro files and tools. QmlDesigner 4.12.4 Visual Designer for QML files. QmlJSEditor 4.12.4 Editor for QML and JavaScript. QmlJSTools 4.12.4 Tools for analyzing Qml/JS code. QmlPreview 4.12.4 Qml Preview Plugin. QmlProfiler 4.12.4 Qml Profiler Plugin. QmlProjectManager 4.12.4 Qt Quick support Qnx 4.12.4 Adds support for QNX to Qt Creator. QtSupport 4.12.4 Provides support code for build systems. RemoteLinux 4.12.4 Support for deployment to and execution on a remote Linux host. ResourceEditor 4.12.4 Editor for qrc files. ScxmlEditor 4.12.4 Visual Editor for SCXML (State Chart XML) files. SilverSearcher 4.12.4 Adds possibility to use SilverSearcher tool as an alternative mechanism of find in files StudioWelcome 4.12.4 Qt Design Studio Welcome Page. Subversion 4.12.4 Subversion integration. TaskList 4.12.4 Use .tasks-files to populate the Issues view. TextEditor 4.12.4 Text editor framework and the implementation of the basic text editor. Todo 4.12.4 Adds pane that lists all TODO, FIXME, etc. entries in comments. UpdateInfo 4.12.4 Displays Update-Infos for Qt Installer Framework-based Updaters. Valgrind 4.12.4 Valgrind Plugin. VcsBase 4.12.4 Version Control System Base Plugin. WebAssembly 4.12.4 Helper for WebAssembly projects. Welcome 4.12.4 Secondary Welcome Screen Plugin. WinRt 4.12.4 Helper for Windows Runtime projects. (C) 2020 The Qt Company Ltd

Because of this post I waited a long time before just now moving to Ubuntu 20.04. I am now: Linux ubuntu-20 5.4.0-40-generic #44-Ubuntu Qt Creator 4.11.0 Qt 5.12.8 I am relieved to say Creator seems as fast as it used to be :) I don't use anything remote. So for anyone reading this, I think it's OK to go ahead with 20.04 + Qt Creator.

Looks like Cppcheck is now a passive thing rather than something you explicitly run? There's no entry for cppcheck under the analyze submenu, but I'm now seeing cppcheck's output as code warnings, so I'm content.

@hskoglund OK. I will wait that my computer will be OK to have the latest Windows 10 version. I have the 1909 and the latest is 2004. And i will wait for a new version of Qt. Or i will reinstall Windows and all my softwares, but it takes a long time. And thank you very much for your help. Best regards.

Hi, Can your provide a minimal project that shows the issue ?

@J-Hilk Ok, now I understand and found Clang Code Model you are reffering to... So 'under the hood' Qt Creator checks my code with Clang 10.0.0 version which does not have <ranges> implemented. Thanks! [image: 4d134673-6f34-4a5f-a7dc-6ea9f5e1eab9.png]