Qt Creator and other tools

Half way there: Stop waiting on a failed build and it only took a decade. In another one it will stop the current project too I'm sure :)

You can try asking for review / information on Qt mailing lists. Also, some of the reviewers CCed on gerrit are active on this forum, if you get no review for a long time it might be good to politely ping them.

hey Joe - it doesn't seem to change the ACP chat window in Creator. I can zoom everything, of course, but that's not what I want.

Compiling Qt yourself for the right compiler version is the right way to go. One simple workaround is to rename the folder of the Qt installation, then uninstall MinGW. Even if it tries to uninstall Qt as well, it will not find the folder. After that you can (and really should) rename the Qt folder back to its original name (some tools have their path baked into the executable).

I think I figured out what is happening. I did not have a look at build_qtcreator dir (my bad). cmake -G Ninja "-DCMAKE_PREFIX_PATH=../install_qt;../libclang" ../qtcreator cmake --build . --parallel produces a valid app bundle called Qt Creator inside build_qtcreator dir. It references libs from install_qt so it can be run only locally. cmake --install . --prefix ../install_qtcreator produces invalid app bundle in install_qtcreator dir. This app bundle does not work even locally. The script SIGNING_IDENTITY=- ./scripts/build.py --src . --build ../build_qtcreator --qt-path ../install_qt --llvm-path ../libclang --no-sbom --no-dmg --no-zip produces valid, relocatable app bundle with all the dependencies being packed inside. The problem seems to be solved. Thanks everyone.

Just set the environment variable QT_FORCE_STDERR_LOGGING=1.

@cristian-adam something like that would be great.

Hi and welcome to devnet, Did you already follow this pinned thread about accessing the bug report system ? In between, I updated the bug report with your findings but don't hesitate to try again and add more context as needed.

Hi, and welcome! @BRNany said in CMAKE_AUTORCC was removed from the default cmake project?: My question is: WHY ISN'T AUTORCC ENABLED BY DEFAULT? If I create a project using "CMake with Qt 5 compatibility", the AUTORCC is already enabled by default... @SGaist is correct. CMAKE_AUTORCC is discouraged now: https://qt-project.atlassian.net/browse/QTBUG-87643 https://qt-project.atlassian.net/browse/QTBUG-141364 explicity process each .qrc file using qt_add_resources(). The recommended approach in Qt 6 is to NOT have a *.qrc file at all. Instead, add your files directly to qt_add_resources().

Hi Alex, thanks for your reply. I confirm that with MSVC debugger it works: [image: 814063ec-7328-400e-989d-037dab507ded.png]

@nnpyro Try Qt Creator 21. There are fixes for this use case.

@Irimitlad said in How to fix missed libicui18n.so.74 when adding qmake to Qt Creator?: libicui18n.so.74 => /usr/local/lib/libicui18n.so.74 (0x00007457a4200000) Why is it looking in /usr/local/lib? Did you install this lib by yourself? Regarding installer being stuck: take a look at https://wiki.qt.io/Online_Installer_4.x#Selecting_a_mirror_for_opensource

@Nils-Sjoberg Thought about that, thanks

Thx for explanation what the problem was. That is what I need. Marked topic as solved