Qt Creator and other tools

Hi, AFAIK, no however, there's an old tool described here to transform doxygen documentation to qch files. Since the gcc doc is based on doygen, that might fit your need. Hope it helps

Occasionally, I just have to rebuild the whole project for modification to work. Is it true or I've done something wrong? You've probably done something wrong or your project is so complicated that make looses track of what's what. When modify a file, and rebuild, does qmake have to check all the files to see if it is update to date? qmake just generates make files. It's the "make" (or "nmake/jom" in case of MSVC toolchain) that looks at what changed, what are the dependencies and what needs recompiling/relinking. If Qt Creator has a native build system(like that in Visual Studio) Qt Creator supports a couple of different build systems - qmake, qbs and CMake are some of them. Those systems generate make files for the "native" make, configured for each platform and toolchain via Kits.

@aha_1980 Done: https://bugreports.qt.io/browse/QTCREATORBUG-23201

@Nick111 You can use x86 on x64 if you don't really need x64

@Kimmo Hello! I have added $(IntDir)\uic\%(RelativeDir) as the Output Directory and now it compiles successfully. Thank you.

Thanks for the infos ! I completely forgot about that tool.

There is a task for this in Jira: https://bugreports.qt.io/browse/QTCREATORBUG-9488 If you want this feature, please REGISTER THERE AND VOTE FOR IT!

@Blue-AKKO I just checked the uic (the tool which generates the code from ui files) parameters and could not find anything for that. I suggest you ask on the Qt developers mailing list.

@aha_1980 Cross-compiling has always been done by setting CC to the correct compiler. Creator does not build your project, make does. That's the reason thrse old habits still apply. Ah, I see. I still think QtCreator could set up the compiler-related env vars for you before launching the build, but I'll keep using the CC/CXX then.

@JonB By default, i.e. add PATH=$(ExecutablePath), it doesn't work, the result is as below: PATH=$(ExecutablePath)$(LocalDebuggerEnvironment) whichs is equivalant to: PATH=$(ExecutablePath) PATH=%PATH%;$(QtDllPath) The one below works, the key point is not to check Inherit from parent or project defaults. PATH=$(ExecutablePath)$(QtDllPath) BTW, where to report the bug?

@SGaist Thanks! Right, so it seems to be better to live with the limitation and keep the implementation in main.cpp.

@sandro4912 nope. write small qt program to do it. Should be pretty simple if thats the patthern the warnings has.

Hi It's not that simply, it seems. While it accepts the -stylesheet cmdline param C:\Qt\5.13.1\msvc2017_64\bin\assistant.exe -stylesheet e:\test.txt test.txt QWidget { background-color: rgb(46, 47, 48); color: rgb(255 255, 255); } [image: Screenshot-04-11-2019-20-12-53.png] It didnt use the color tag for changing text color. I tried some other stylesheets but at no point,the color would change so not sure this can be useful but i felt i should mention it anyway.

@aha_1980 said in Can it support more actions in "Edit Mode / File System": You can move files by renaming them, i.e. press F2 and then change the (relative) path of the file. It will update the project accordingly. It's ok, but not very convenient. If it can be manipulated as in a file browser, it'll be very convenient and efficient. For your other questions: There is a patch under review that implements drag&drop: https://codereview.qt-project.org/c/qt-creator/qt-creator/+/275376 I prefer cut & paste more, I'll wait and hope there is an update about this, and using VS with Qt plugin now. For everything else feel free to add suggestions at bugreports.qt.io. OK Thanks

@aha_1980 The challenge I have with doing things in the Compile Output pane is that if I click in the pane, it takes me to the offending line. So, searching isn't feasible.

I have an ssh key added to the git... The problem was that it was cloned using http instead of ssh. Now sorted :)

I was able to update Qt, thanks for helping me out.