Qt Creator and other tools

@Marian-Saenger-DE can you post a link to the bugreport here so others can follow? Thanks!

@surajgoswami You would need to patch the binaries (Qt libs) to change the rpath, but reinstalling Qt is easier.

indeed, now there was a button

Hi, I have same problem, I try to do too many things but, It can not be solved.Caould you help me?Thank you.

@Christian-Ehrlicher Noted.

Thank you very much for all of your help — I’ve already resolved the issue~ I referred to the following post: https://stackoverflow.com/questions/65263280/qt-android-unable-to-debug-error-unable-to-find-dynamic-linker-breakpoint-fun/65275623#65275623 Here are the steps I took: 1.Installed CMake and Ninja using the MaintenanceTool. 2.Changed the CMake Tool setting to CMake, and the CMake Generator to Ninja. 3.Removed the line handle SIGTRAP nopass nostop noprint from Preferences → Debugger → GDB. After deleting the build directory and rebuilding the project, everything is now working correctly.

@Asperamanca It is, just click the drop-down menu included in the magnifying glass: [image: b1321093-22d9-41e7-9642-e4d0b3939461.png] Regards

i get it,set system path

@horatb offline installers are still available to commercial customers. But I get your point. As for issue resolution, it highly depends on Heroku's capacity to fix the issue(s) they are currently experiencing.

@garlicbox said in How to install Qt Creator on Windows 7? Last working version?: Can it be configured? And how to do it? Yes. Go to the Kit configuration. Add your custom Qt build there. If needed also the VS2017 compiler (should have been auto-detected by QtCreator). And then create a Kit with your Qt version and the compiler.

OK thanks - I'll work it all out ... D.

@Nikolay-Levun Answered in your thread

@SGaist Thank you!

Hi, The most simple way is to go to the bug report system and check the open issues. Find one that interest you and start hacking on it :-)

Maybe you can get around this problem by creating an empty qt,conf file at a place with higher priority than the current directory, I'm thinking of storing it in your executable as a resource ( i.e. :/qt/etc/qt.conf) more here: https://doc.qt.io/qt-6/qt-conf.html P.S. If Qt does not like an empty qt.conf, try (almost) the same as above: [Paths] Prefix = .

@ziller - Thanks for the reply, correct when I built Qt from source there weren't any examples (as I didn't build the doumentation), but as I did use the online installer initially for Qt6.8.1 it added those examples in the correct place yet they were still not seen after what I believe I did, which was install the stand alone QtCreator 16. It was at this point 'I think' the versions drop down for the examples disappeared, but I cannot be sure, hence posting). After posting I then installed from the maintenance tool the latest Qt6.9.1 MSVC, yet still no examples, but also a hint was that those newly installed kits didn't appear in the auto detected list. This was how I ended up seeing the 'Link to Qt' option which once done brought back all of what should of been the auto detected kits, and the examples for the versions installed by the maintenance tool. What's not clear is why they disappeared (I'm assuming the QtCreator 16 install as a stand alone wiped a settings/configuration for QtCreator - I'm going to try and look deeper at that today as time permits.

@supaiku_ you call that necroposting? This is necroposting! I just discovered resources_big via this thread and it is a-maz-ing. It's also now documented: https://doc.qt.io/archives/qt-5.15/qtcore-cmake-qt5-add-big-resources.html I have a chunky-but-not-altogether-unexpected ~40MB referenced in my qrc, and it was blowing up with the dreaded "virtual memory exhausted: Cannot allocate memory" when compiling on a 32-bit target. No amount of exhaustive and exhausting memory tuning could prevent memory usage (not even involving swap!) from hitting the 2GB critical limit. I simply removed my qrc file from set(PROJECT_SOURCES in CMakeLists and reinstated it in qt5_add_big_resources(PROJECT_SOURCES instead. And boom, compilation blasted through the rcc step and barely broke 1GB usage getting the whole job done.

@Axel-Spoerl said in Creator crashes by opening a special cpp-file: Does that happen with any file or just with that specific one? I have worked with a lot of files the last days, so I think its the only file.

Hi and welcome to devnet, Are you trying to implement some sort of wizard ? If so, take a look a QWizard.