Qt Creator and other tools

Why are you adding the src folder to INCLUDEPATH?

Your information helped me solve a bug that has existed for years in the system! Thank you so much!

@Sriep Ok! I have got it working now. I needed to copy two folders, maybe deleting debug stuff. C:\Qt\5.8\msvc2015_64\qml\QtWebView C:\Qt\5.8\msvc2015_64\qml\QtWebEngine I had a similar problem with QtLocation and QtPositioning.

Hi, It's this one: http://lists.qt-project.org/pipermail/qt-creator/

I don't know if it's related, but I would try to cross compile from linux To Windows in order to check if problem is solved. All start from a application that print a text document in PDf format using ARIAL font: sometimes I need to correct the date and this is possible editing the file with Adobe Acrobat. Well, this is possible only if I compile my app using Qt from Linux (Arial font still remains the same), while using QT from Windows Arial font seems to have a different feature that doesn't allow to edit it directly.

@SGaist said in Qt Creator : how to set cmake option -Wno-dev?: In the build configuration I was hoping to give me a concrete example, since I already know this and have tried different options, which didnt work ... But for all others, there is CMAKE_SUPPRESS_DEVELOPER_WARNINGS option in the Build Settings.

This is the guide to get the Assitant as a executable instead of a full bundle inside your own application bundle: Copy the Assistant executable in your own Application bundle in the MacOs folder. Change the rpath to link to the Framework directory: install_name_tool -add_rpath '@loader_path/../Frameworks' YOUR_APPLICATION.app/Contents/MacOS/Assistant Run the macdeployqt on your Application but also with this command: macdeployqt YOUR_APPLICATION.app -dmg -always-overwrite -executable=YOUR_APPLICATION.app/Contents/MacOS/Assistant Note: The -dmg tag is optional, please test it first without the parameter. Please make sure the Frameworks directory contains the following files: @rpath/QtHelp.framework/Versions/5/QtHelp @rpath/QtWidgets.framework/Versions/5/QtWidgets @rpath/QtGui.framework/Versions/5/QtGui @rpath/QtCore.framework/Versions/5/QtCore /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit @rpath/QtPrintSupport.framework/Versions/5/QtPrintSupport @rpath/QtNetwork.framework/Versions/5/QtNetwork @rpath/QtSql.framework/Versions/5/QtSql /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL /System/Library/Frameworks/AGL.framework/Versions/A/AGL /usr/lib/libc++.1.dylib /usr/lib/libSystem.B.dylib You can check where the rpath is leading with the following command: otool -l YOUR_APPLICATION.app/Contents/MacOs/Assistant Make sure it returns this item: Load command 28 cmd LC_RPATH cmdsize 40 path @loader_path/../Frameworks (offset 12) It's possible to have multiple LC_RPATH, so don't worry if there are also others.

@hunger said in Qt Creator : RAM consumption too much ?: That is expected. Indexing in Creator means that a compiler runs over all your code and all the data that produces is retained for code completion, refactoring and navigation tasks. Atom does not do most of that stuff, so it needs way less data. That data is what makes Creator useful:-) Ok, I just checked: For the current project (C++) qtcreator 1.3GB, and if it runs longer it comes to 4,1GB ... Atom Code Completion added some 100MB (to the current 200MB, so all together 300MB). Recatoring offers many functions, but I hardly use them (Maybe I should ?!?). Navigation tasks is useful, yes. But 1-3 GB (3-10x) more than Atom ?

Are you using the same version of OpenSSL that is used to with the pre-built Qt Creator ?

For Qt 4.8.6, I managed with the following, but still not sure about how to proceed for Qt5 without building whole qtbase module. make sub-tools-bootstrap make sub-moc sub-rcc sub-uic

@hunger : Creator should default to the Codeblocks versions of make and ninja generators. So that should work out of the box;-) Why is it like that? Because Creator parses the Codeblocks files to extract information about the cmake project. So without the Codeblocks file it does not have any information on what you are building. Of course, this is well documented :). But it tunred out the above is not completely true. Than once run with a codeblock generator, if I switch off the second generator again (i.e. remove the second generator, which is Codeblock), the source tree is displayed normally, and no warnings are to be seen again. @hunger : IIRC it should also warn when you select a cmake generator without Codeblocks support in the kits page. It should, but it doesn't. I just checked it. Could you give an example how this message should look like ? @hunger : PS: You want to give ninja a try. Just install ninja, mak sure it is in the PATH anr switch to the ninja generator (with Codeblocks). With ninja it will also work. But I set make, because I wanted to test icecc with Qt creator. It turned out this is not an issue. Qt creator works with icecc with both ninja and make.

Hi, Did you do the change on an already configured project ?

@jsulm: thanks for the suggestion. I created a change request here. --henrik

After setting up OpenOCD so I could deploy and debug application and trying to debug application QtCreator crashed every time I stopped the debugging. But after checking the magic option "Use asynchronous mode to control the inferior" in Options>Debugger>GDB Extended it finally worked. Oh and also I needed to install winusb drivers for st-link using zadig. Hope someone find this useful.

That use-case is not covered out of the box, sorry. Sysroot is intended to be used for cross-compilation, not for in-chroot compilation. So I do not think that is what you want. There are two hacky ways to build something in a chroot though: I just installed my Qt Creator inside the chroot and use it from there. That is probably the easiest approach, but leads to way more libraries being installed in the chroot than strictly necessary. I mostly work on Qt Creator itself, so the dependencies of the Qt Creator I run as an IDE and the program I work on do match up fully anyway:-) There were embedded projects that went down the wrapper-way. Basically they used wrapper scripts for cmake and some other things that forwarded calls into a VM/chroot/container and executed them there. The tricky part here is to make sure the sources (preferably including system headers!) are in the same place inside and outside the VM/chroot/container. Otherwise you will need to map paths back to the outside environment for Creator to actually jump to errors and such and the code model will also break:-) As for running in another environment: Creator supports SSH-ing into another machine and run/debug stuff there. With a bit of work it can even automatically copy the binaries into place and everything. So if you just need to run something in a fully defined environment of an VM/chroot/container, then that is easy if you can manage to run a SSH server there and to install gdbserver.

Thank you for your help, koahnig & jsulm...

@koeniee Indeed. Xp still works fine. its just not safe to use near internet.

Hi and welcome to devnet, I'd recommend bringing this question to the interest mailing list. You'll find there QtVirtualKeyboard developers/maintainers. This forum is more user oriented.

Qt Creator 4.2.1 on macOS.

@koahnig If you promise not to tell anymore, i just discovered that it can actually autocomplete in .pro file :) Very handy. ;)