Qt Creator and other tools

Additional note: I built a new CMake file (using a file from another project and editing it) for an existing qmake project and attempted to build it. All components built until it got to building the UI. For some unknown reason, the resulting "ui_mainwindows.h" file, which is in it's normal place in the build folder was not found by CMake. I changed CMake to turning on AUTOUIC and it built properly. Then changed it back to the qt6_wrap_ui method and it continues to build properly.

Hi @JacobNovitsky, try selecting the lines, then Shift-Tab one or more times? :) Cheers.

Currently I am able to build my shared objects. I was able to simply use add_library(), as well as target_include_directories(). However, since qt_add_qml_modules() does a lot more under the hood I still have more work to do. I was able to auto-generate qmldir files (using the write capability of CMake). I am currently trying to invoke qt5's qmltyperegistrar with parameters to correctly generate my .qmltypes files, however I seem to be missing the *_metatypes.json, my *_*Plugin.cpp file, and my *_qmltyperegistrations.cpp is very bare. I am unsure if there is an additional stage before the type registration, there are references to lint as well as auto_MOC.

Which CMake version are you using?

Just click "Apply" and the error will go away. At least this is what happens on my machine 🙂

I am not sure I follow what you are attempting to do, but mention of the private-dev packages perked my ears. In a "Debian/Ubuntu"-esque environment, there are multiple *-private-dev packages, some of which are required for compiling additional libraries like QtMqtt. apt search "private-dev" for a long list for both Qt5 and Qt6. This may be the one you are looking for. qtbase5-private-dev/jammy-updates,now 5.15.3+dfsg-2ubuntu0.2 amd64 [installed] Qt 5 base private development files

I created a minimal example (default console application without anything else). It fails in Qt Creator with the same error. On the command line, it succeeds. The trick seems to be that the path to ccache needs to be prepended in the project environment. It's not sufficient to add it to the build environment.

@cristian-adam I changed to https://download.qt.io/development_releases/prebuilt/libclang/libclang-release_60-windows-vs2015_64-clazy.7z and it worked! Thank you very much!

Thanks @JonB. But there's still a problem. As I am on a Mac, I cded to ~/Qt/'Qt Creator'/Contents/MacOS' and ran ./'Qt Creator' -tcs. Qt Creator opened up, with auto-completion and rest working, but when I closed the app an opened it again, no information was preserved, e.g. font size, Use FakeVim, etc.

It's a regression in Qt Creator 11.0.0. Qt Creator 10.0.2 works fine. See https://bugreports.qt.io/browse/QTCREATORBUG-29440 Take libcpp_stdtypes.py and replace your version from c:\Qt\qtcreator-11.0.0\share\qtcreator\debugger\libcpp_stdtypes.py and it should be fine.

@sierdzio said in ninja subcommand failed: How to get more info?: I have not tried this myself, but the documentation mentions a way to disable qmllint warnings, see: https://doc.qt.io/qt-6/qtquick-tool-qmllint.html#settings Yes, I've seen that page, but the .ini file seems to be ignored and I don't know how to pass these settings through cmake

@SGaist Hi. Of course. I've divided it into two sections: https://bugreports.qt.io/browse/QTCREATORBUG-29435 https://bugreports.qt.io/browse/QTCREATORBUG-29434

@JonB Ah ok, both are ext4. But i think the problem starts earlier, because the open() is already called with different parameters. It could still be some platform related reason, if the call is made from a lib or so, which differs. The Qt version is in both cases 5.15.3.

@cristian-adam Thanks for work around apparently it does work. Interesting is that in the new installation was only the libcpp_stdtypes.py available. Even though I have tried to debug a couple of times. Now with the version of creator 10.0.2 (I believe) libcpp_stdtypes.pyc was created immediately when debugger was started.

@sierdzio Ok. Thanks for letting me know. the_cowboy

@JKSH sure, except I didn't remove or delete the kit in any way. QT just decided it was gone after I restarted m computer

@SGaist Can you loop in anyone who has any idea about this. I see for some of my projects for all configurations the macros are enable and for some only for few configurations enabled. Maybe some option is not enabled. can Identify which one

@JacobNovitsky said in How to open qt project in Qt Creator in one click or macro or shortcut in Ubuntu: locate QtCreator Use which: which qtcreator"

Hi, Try with a different mirror. For the size difference, there are the libraries for debug and release builds. The former are not installed by default with your package manager. As for Androïd build, unless your distribution explicitly provides it (which is highly unlikely), you need the installer (or build it yourself).