Qt Creator and other tools

Judging from the source code of qdbusxml2cpp: it cannot generate NOTIFY declarations for properties at all. Christian

@OlegD said in How to split window like that: QT redactor What's this? i would use better splitting on left angle And what does this mean?

@ecorm said in Installing Qt Creator for colleague: I've found the --reset-qtaccount option from the online installer. Is it as simple as this? Use my own credentials for the installation Run the installer again with --reset-qtaccount Having my colleague enter their Qt Account credentials in the Maintenance Tool after I handover the development machine to them? I've had my colleague create their Qt Account with a temporary password that's been shared with me, with the understanding that my colleague will change their password once they receive their development machine. With that information in hand, I tried using --reset-qtaccount option that I discovered for the installer. However, when the installer gets to the Installation Folder step, it complains about the destination directory already existing. It turns out that the MaintenanceTool also has the --reset-qtaccount option. I've tried this using my colleague's Qt Account credentials, and performed an update operation. However, the next time I launch the MaintenanceTool, it's still my email that shows up as the Qt Account username. If I enter my colleague's Qt Account credentials, it complains that it doesn't match the ones used for installation. I ended up reinstalling from scratch using my colleague's credentials with the temporary password. I wish there was a cleaner way of doing this without having to share temporary passwords. In case anyone is wondering, I'm taking this opportunity to document the steps involved in setting up a new development environment, so that a new programmer can do it themself using their own credentials. I should also clarify that the new programmer can ultimately use whatever editor or IDE they want, as long as no major changes are required to the CMake scripts. It's just that I'm required to provide them with a working IDE that can debug our code, so that they can hit the ground running.

on clean ubuntu 22.04: 7.0.2 - creator crashing my app build from source 8.0.0.-beta1 - exit ok (but not print exit code 123)

Hi and welcome to devnet, You need to provide more information: Qt Creator version Qt versions How you installed all of that On which OS

After quite some digging I found the solution to "how to install the heob plugin". On Windows you need to activate the "Valgrind" plugin (!!) in order to see the "Heob" entry in the "Analyze" menu - despite Valgrind is only available on Linux. You can activate the Valgrind plugin in the menu "Help -> About plugins ..." The documentation does not tell you this, so comments like the one from @Pablo-J-Rogina are not helpful either.

@davecotter Without knowing what platform or debugger you use? This is a debugger thing rather than a Qt Creator one, I use gcc & gdb under Linux, I do not get any "leak detection reports" on exiting. Unless I were to run it under valgrind.

@mzimmers said in configuring for cross development: @cristian-adam thank you for the detailed reply. I'm still trying to understand how the CMake process operates, so I have a few more questions, if you don't mind: do I understand correctly that Creator is attempting to use Windows-GNU.cmake in the build? If so, is this correct? This is what CMake is doing. Qt Creator has nothing to do with it. CMake is receiving a gcc.exe and it looks at the host platform ... Windows so it picks up its Windows-GNU.cmake internal code path and tries the best out of it. Since this is not a MinGW GCC toolchain is bound to fail. you mention a toolchain file. Is this the same as a CMake Source File (as shown in the Windows Explorer window)? if I were to make my own toolchain file, where should it reside? I don't want to modify the contents of the .espressif/tools directory. You need a esp.cmake text file, which we would refer as toolchain file, and then in Qt Creator (or commandline) pass the CMAKE_TOOLCHAIN_FILE variable pointing to this file. would you consider this a bug in the Espressif toolchain? If so, I can submit an entry on their github. I personally have no interest in the esp toolchain, it's the first time I've heard about it. Their toolchain is not buggy, it's just doing extra work and makes it a bit hard to follow, it's not as easy to copy paste, it needs the extra API file (e.g. $ENV{IDF_PATH}/tools/cmake/utilities.cmake), etc. But on the other hand you might need to follow their documentation about the CMake support.

It looks like your clazy checkout doesn't handle your llvm/clang installation. You can get llvm 14.0.3 and clazy 1.11 from https://download.qt.io/development_releases/prebuilt/libclang/. If you want to hack on clazy itself, you can still get the archive and compile it against it. Make sure you add CMAKE_PREFIX_PATH=/path/to/llvm-14.0.3/. Or you can install Qt Creator 7.0.2 and get clazy-standalone installed automatically.

Now everything ok, I pointed to the folder with "qt version". After upgrading Qt to 6.3.0, it is located in /qtpath/Tools/QtCreator/share/qtcreator/, although the file 'qtversion.xml' located farther: /qtpath/Tools/QtCreator/share/qtcreator/QtProject/qtcreator. [image: i-DR98sDj-XL.jpg]

Ran qmake in the terminal, got the following: make[2]: *** No rule to make target '/opt/EDTpdv/libpdv.a', needed by 'libcommon.so.1.0.0'. Stop. make[2]: Leaving directory '/home/sam/workspace/sample/RealTimeThreadFuncs/common' make[1]: *** [Makefile:70: sub-common-make_first] Error 2 make[1]: Leaving directory '/home/sam/workspace/sample/RealTimeThreadFuncs' make: *** [Makefile:92: sub-RealTimeThreadFuncs-make_first-ordered] Error 2

I just found this comment to a quite old bug report from 2014 which might be related: https://bugreports.qt.io/browse/QTCREATORBUG-11510?focusedCommentId=233279&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-233279 Since we don't want to run arbitrary processes while parsing the project, the evaluator simply assumes that the process could be run successfully and thus packageExists returns true. However I do not understand that, and also don't know how to resolve the issue.

Ok, apparently the library did not contain much code. Adding more code it now correctly shows that it is a dynamic library also with ldd.

Hi, You can manually check against the set of templates but there's no automated way for that. Out of curiosity, why do you need that information ?