Qt Creator and other tools

@JoeCFD Found the solution by googling, this post contains an "atomic bomb", an ELF stripping/cleaning command: strip --remove-section=.note.ABI-tag libQt6Core.so.6.2.2 To get Qt Creator 6.0.0 to work on Ubuntu WSL, use this stripping command: strip --remove-section=.note.ABI-tag ~/Qt/Tools/QtCreator/lib/Qt/lib/libQt6Core.so.6.2.1 and then to be able to build and run a Qt6 program, apply the same patch on the core dll for Qt 6.2.2 itself: strip --remove-section=.note.ABI-tag ~/Qt/6.2.2/gcc_64/lib/libQt6Core.so.6.2.2

The screenshot is Qt Creator 6.0.

@artwaw yes, here is example of test CMakeLists.txt: cmake_minimum_required(VERSION 3.5) project(SingletonMultitone LANGUAGES CXX) set(CMAKE_CXX_STANDARD 17) set(CMAKE_CXX_STANDARD_REQUIRED ON) file(GLOB SOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} *.cpp* *.h*) add_executable(SingletonMultitone ${SOURCES}) Simple_Project.zip

@Mikeeeeee Hello! You can try Qt Creator 6.0.0 compiled by Qt 5 - https://download.qt.io/snapshots/qtcreator_qt5/6.0/6.0.0/27/ By the way, Qt 6.0.0 compiled with Qt 6 has the scale issue on UHD monitors - https://bugreports.qt.io/browse/QTCREATORBUG-26643

You most likely didn't set the right 'Qt Creator build' path in the wizard. How does the beginning of the generated CMakeLists.txt file look for you? It should contain something like list(APPEND CMAKE_PREFIX_PATH "C:/dev/creator/master/build-qt-creator-6.2.2-amd64") where the path should point to the local directory you built Qt Creator in.

@J-Hilk said in Issue in Parsing file in Qt: when I switch to the android kit Thanks for the tip! I disabled the Android kit for my project and the code model is working again in my editor.

This "solution" is just to enable syntax highlighting. Try the following very basic code: __global__ void hello() { printf("This is a test"); } int main(int argc, char* argv[]) { hello<<<1,1>>>(); return 0; } The code above is a very basic example for CUDA source file that includes a kernel definition and will cause a lot of problems with Qt Creator. I am guessing the same will happen if we use __device__. Adjusting the MIME type for C++ to include CUDA helps only with the syntax highlighting. Ultimately CUDA, while being very, very similar to C/C++, is a different language that requires its own language model that is not included in Qt Creator as well as a compiler, which - through CMake - can somewhat be integrated into the IDE. If you want to develop with CUDA and CMake I would suggest using VS Code or Visual Studio with the second still (2019 edition) having a not that great support for CMake). Last but not least the devs from NVidia have done a really sloppy job in regards to offering integration of the CUDA infrastructure in popular IDEs. It takes hours if not days to make a setup that just works.

This is indeed a known issue, see e.g. https://bugreports.qt.io/browse/QTCREATORBUG-26647. It will be fixed in Qt Creator 6.0.1. Meanwhile, you can try using a snapshot from https://download.qt.io/snapshots/qtcreator/6.0/ .

Also, Qt Creator 4.4.1 is quite old. Please try with a more recent version, like Qt Creator 6.

@Christian-Ehrlicher Thank you very much.

@J-Hilk That's right! Thank you very much. Although it's strange that the state won't be saved by default (via "open" button). (because VS will)

Restarting my computer removed the old paths. Not sure if that's the best solution, but it's a solution. [image: ca441c7a-bd0e-43d4-a35f-b5344291cc37.png]

Hi, There's no Qt based compiler. On macOS Xcode is used to build the framework.

@raven-worx Hi thanks for the question. So a reasonable machine really. 16gb Ram on 8 core Intel i7-9700 @ 3.00mhz

@mrjj Hi. The interesting case is when a folder contains a subfolder with files but without any file in it. I say that‘s weird because The folder management is completely different from Windows. In Windows you can have folders with subfolders with files and no file in these folders..

This worked, thanks! I guess it was trying (and failing) to import both the .pro.user file, and the backup ones. Removing them all fixed the import.

@VikiWang For qmake I don't know. If you don't find something in the qmake reference I think you're out of luck.