Qt Creator and other tools

My bad ... I forgot to make docs and make install_docs. Looks like this will take awhile, but it seems to be OK.

That's what I wrote, you have to compile the module yourself for that version of Qt.

Thanks @SGaist and @mchinand for the detailed discussion, let's wrap this up. Summary PRE_TARGETDEPS helps detect changes in static libraries. QMake implements MyModule .depends, but it's missing MyModule. target_full_path which makes it inconvenient to use PRE_TARGETDEPS, and especially QMAKE_POST_LINK. Some platform specific hacks are necessary. Working solution Here is an example of a complete solution which detects source changes in all modules, including static libraries. The solution uses a project wide hack, which is not that bad after all. === ./.qmake.conf === # # QMake will find .qmake.conf automatically. # PROJECT_ROOT = $$PWD === ./static_libs.conf === # # Assumes DESTDIR is configured project-wide so all binaries are written to one place. # windows { MyStaticLib_FULL_PATH = $$shell_path($$DESTDIR/MyStaticLib.lib) # ... Other static libraries in the project } else { MyStaticLib_FULL_PATH = $$shell_path($$DESTDIR/libMyStaticLib.a) # ... Other static libraries in the project } === ./MyStaticLib/MyStaticLib.pro === TARGET = MyStaticLib TEMPLATE = lib CONFIG += staticlib SOURCES += ... HEADERS += ... === ./MySharedLib/MySharedLib.pro === TARGET = MySharedLib TEMPLATE = lib INCLUDEPATH += ../MyStaticLib SOURCES += ... HEADERS += ... win32:DEF_FILE = MySharedLib.def LIBS += -lMyStaticLib # # NOTE the below 2 lines. # include($$PROJECT_ROOT/static_libs.conf) PRE_TARGETDEPS += MyStaticLib_FULL_PATH === ./MyApp/MyApp.pro === TARGET = MyApp TEMPLATE = app INCLUDEPATH += ../MySharedLib SOURCES += ... HEADERS += ... LIBS += -lMySharedLib === ./MyProject.pro === TEMPLATE = subdirs SUBDIRS += MyStaticLib \ MySharedLib \ MyApp MySharedLib.depends = MyStaticLib MyApp.depends = MySharedLib

@Christian-Ehrlicher Code was successfully compiled, but The error is still prompted. This is a QT for Android Application. It could be a problem with the NDK.

@Patisson can you try to find qtcreator_processlauncher.exe on your installation and check it can be manually started from a terminal?

@Merlino said in QtCreator problems after update on RHEL8: @JKSH I have tried with https://download.qt.io/snapshots/qtcreator_qt5/7.0/7.0.3/202/ because your link is no longer available, unfortunately it didn't work for me. That's a shame. Thank you for testing. In your bug report, Christian Maurer mentioned that switching back to kernel-core-4.18.0-348.23.1.el8_5.x86_64 worked for him.

I fixed mine by changing <Keyword>Qt4VSv1.0</Keyword> to <Keyword>QtVS_v304</Keyword> In my .vcxproj file. I had to repoint it towards the install location, but no longer got the "Object reference not set to an instance" popup and can now build.

Posted an issue: https://bugreports.qt.io/browse/QTBUG-104450

Hello, just change the language in settings>> language and time and change the language to English this will update the language in the designer.

I had to work on an old laptop (2-core Sandy Bridge CPU) for the past 3 months instead of my Ryzen 7 desktop PC, and I've noticed that code indexing and auto-completion is incredibly slow in Creator 7, and much much better in Creator 5 on the same laptop. With no visible differences in functionality.

@JonB @cristian-adam It was an MSVC compiler problem. Regarding Unicode, there was a part that did not match Creator. This has been fixed and the typing delay is gone.

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)