Qt Creator and other tools

@Christian-Ehrlicher said in Qt Creator: cmake errors after downgrade of MSVC compiler: 17.9 should also work. Make sure to start with a clean build dir and also no CMakeLists.txt.user in the source tree I did everything, but forgot about .txt.user Will try that... EDIT: However, after the torturous downgrade/upgrade experience, my VS debugger decided to behave, so I'll keep you advice for the future.

I've opened up QTCREATORBUG-33213: Model Context Protocol (MCP) support.

@Iann29 Hi, I know this is a little late and I was running into the same issue but this is what fixed to for me. I went into the kit menu and I a kit for Desktp Qt 6.9.1 MinGW 64-bit (default) that had always come up as an unsupported/unavailable kit. However, all I had to do was clone it in the kit menu, see here. [image: 468b3f2d-cea4-4c50-bf91-0600151c6c1b.png] Then when I created a new project with Qt Quick Application for Python with PySide6, it let me select not only the python kit but also my desktop one that allows the designer to work.

@gg123 See https://github.com/PeterFeicht/cppreference-doc and the https://github.com/PeterFeicht/cppreference-doc/releases page. The v20250209 release looks like this in Qt Creator 17: [image: 43a19d4f-b4c0-492d-850c-edda915d56e4.png]

@Shap QPlainTextEdit will (should) behave the same as QTextEdit so far as sizing is concerned. They are both for multiline input, and can grow vertically. QLineEdit is for single-line input, and would not grow vertically. Same as the other widgets you talked about.

Thanks for sharing the detailed steps — it looks like you're almost there. The error about the missing ABI usually means QtCreator isn’t detecting the correct architecture for deployment. Adding ``` ANDROID_ABIS = arm64-v8a Double-check that the Kit you're using is actually set up with the correct Qt for Android version and the appropriate architecture. Also, make sure the NDK path is correctly configured in the SDK settings — mismatches there can silently cause issues like this. Running on an emulator first is definitely a smart move. Hopefully with those tweaks, you'll be able to deploy without issues. Let us know how it goes!

I finally managed to get proper help back again, so I'm sharing the solution juuuust in case some other lost soul comes here in search of an answer. Clone the QtCreator source code. Checkout version v7.0.2 (this is the last version that supports Qt5). Build it against Qt5. Select "QtWebEngine" as the help renderer. Not only did rolling back to v7.0.2 + Qt5 give me proper help, but it also fixed a whole plethora of other annoying bugs. And even if there was any actual functionality added since that version, I didn't notice it, so I didn't even lose anything. [image: 681d75c2-ecb0-4a7a-8680-f0fa0267bf36.png]

@AlGig Newer versions of Qt may not support the old Android versions and hardware. The Android version in my phone is 14. It may not make a lot of sense to work with Android 6.

@kkoehne Thank you! I had forgotten I had posted this!

I thought linuxdeployqt does not support Qt6.x.x? Is there an alternative AppImage method that works for Qt6?

@cuijg Could be a bug. You should report it on Qt Bug Tracker: https://bugreports.qt.io/secure/Dashboard.jspa

@weiluI also ran into this problem. I couldn't find a solution to this problem. If you find one, could you explain it? I can add files manually through CMakeLists.txt, but I'd prefer to add them without it

Nice! Thanks

Which version of Qt Creator are you using? On which operating system are you debugging? In case you remote-debug on Android, you might be affected by this bug: https://bugreports.qt.io/browse/QTCREATORBUG-29928

Hi and welcome to devnet, Did you enable the plug-in as suggested in the documentation ?

@JasonWong Keep in mind that this is user forum. You should ask on Qt developer mailing list or file a change request in Qt bug tracker.

@ankou29666 said in CMake warning : the target is mentionned as dependency but not declared: guess that importing Qt::HttpServer module also brings Qt::Concurrent and Qt::Network as implicit dependencies, that don't need to be declared explicitly ? correct, that's why you have to use PRIVATE, PUBLIC and INTERFACE in your target_link_libraries() call: https://cmake.org/cmake/help/latest/command/target_link_libraries.html#libraries-for-a-target-and-or-its-dependents

Ahhh, I see... now that I've taken a break, I didn't realize that my entire process was flawed. The user is going to be adding files to the folder at any point in time, so of course it wouldn't be best to generate those files at compile time, lol. Like you've mentioned, I'll just monitor the folder within C++ and have QML react to the changes. Thank you for the help!