Qt Creator and other tools

@ankou29666 said in CMake warning : the target is mentionned as dependency but not declared: guess that importing Qt::HttpServer module also brings Qt::Concurrent and Qt::Network as implicit dependencies, that don't need to be declared explicitly ? correct, that's why you have to use PRIVATE, PUBLIC and INTERFACE in your target_link_libraries() call: https://cmake.org/cmake/help/latest/command/target_link_libraries.html#libraries-for-a-target-and-or-its-dependents

@thomasGl Did you build in debug mode? Do you see assembly only for Qt libs or also for your app?

Ahhh, I see... now that I've taken a break, I didn't realize that my entire process was flawed. The user is going to be adding files to the folder at any point in time, so of course it wouldn't be best to generate those files at compile time, lol. Like you've mentioned, I'll just monitor the folder within C++ and have QML react to the changes. Thank you for the help!

Whatever it is, it has to do something with your PC or your project. I am using Creator every day on a 3 year old HP ZBook with 64 GB of RAM and openSuSE Tumbleweed. It literally takes milliseconds to find slot functions. Besides, a nice feature for the Designer would be, if on can see in the slot list if a slot funktion exists yet. A * sign or so. Sometimes I have not the overview what kind of slots are connected und I must check it all - what is very slow now. The widget designer shows a list of signals. You can use the autoconnect feature with the on_<ui-element>_<signal-name> syntax. You can also manually connect to a slot named differently. You can use multiple connections, which you set up and disconnect at run time. The "Go to slot" function just implements the autoconnect version in the cpp file that includes the code generated from the form. If the slot is already implemented, it makes Creator jump to it. The logic of when to put an asterisk isn't trivial. The question makes me think whether the cpp file with your implementation is actually super-huge and somehow slowing Creator down. Can you boil the issue down to a small, compilable reproducer?

@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

This looks like a genuine bug. I took the liberty to file https://bugreports.qt.io/browse/QTBUG-137563 for this.

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.

Why are you copying the header file to the build dir? Usually, this is not necessary. @Aleksey_K said in Navigate to header in source tree: navigates me to the header file copied to build dir, not to the original one in the source tree. Usually, this is because of the order of directories in the include search paths. I am only aware of additional preprocessor defines in QtCreator, but not separate include search paths.

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