Qt Creator and other tools

@Mircea Please note that attaching pictures usually does not work in this forum. You need to upload them to somewhere and post links here.

Hi and welcome to devnet, AFAIK, the QtQuick Compiler is a licensed product so you should check with the Qt Company directly. On a side note, it's likely going to be a host tools like qmake or moc so one thing you can try is to copy the one you already have in the binary folder of our self-built Qt.

@jsulm Manage to get kmap2qmap working. So i gave myself priviledges on /bin first. Send the file /bin/kmap2qmap to my embedded device at its /bin location. Did this: cd /usr/share/keymaps/i386/qwertz/ kmap2qmap de-latin1-nodeadkeys.kmap de-latin1-nodeadkeys.qmap A warning came: Warning: keymap file 'de-latin1-nodeadkeys.kmap', line 4: could not locate keymap include Parsing the specified keymap(s) produced 1 warning(s). Your generated qmap might not be complete. The de-latin1-nodeadkeys.kmap file was zipped as de-latin1-nodeadkeys.kmap.gz So i unzipped it as: gunzip de-latin1-nodeadkeys.kmap.gz I went and ignored the waring and gave it a try by exporting : export QT_QPA_EVDEV_KEYBOARD_PARAMETERS=keymap=/usr/share/keymaps/i386/qwertz/de-latin1-nodeadkeys.qmap But that didnt worked becouse the default keyboard was still selected instead of my german one.

Hi! Two guesses: Wrong working directory, missing environment variables.

Adding all include directories reported by GCC to .pro file solved the issue for now but I would still like to know a persistent solution.

@12398890 I don't think CentOS 6.8 will ever become a newer GLibC version - this library is one of the core libs which usually are not updated in the lifecycle of a Linux distribution (only bug fixes). Can't you updgrade to a newer CentOS version? An alternative would be to try to build QtCreator by yourself.

@JanW This answers it better than I could: http://stackoverflow.com/questions/14633454/how-can-i-embed-a-qt-resource-into-a-dll-file Glad it's working for you now though. :)

@sierdzio It is the latest version of Qt creator (4.2.1), but unfortunately with the debugging issue for standard containers. I did not manage to install a previous version in addtion, yet. I do not have an SSD yet. Still on the wishlist as basically the whole new machine is. :(

Hi, @mrjj Where does @TargetDir@ come from ? It is a environment variable? it is a predefined variable you can find a list of them in the following link: http://doc.qt.io/qtinstallerframework/scripting.html#predefined-variables

You're welcome ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)

You can your DEL_DIR for folders.

I meet the same issue today. So i download the older version of Qt.

Hi, Follow @uwer's advices and the link he posted.

Hi, interesting. I had to set this up last week for a work project on armv7a and it worked with the NDK v13. Maybe just parts are affected? Our project uses QML only. Anyway, since the tutorials I found all lead to dead ends, I wrote the steps down that went successful for me. https://stackoverflow.com/a/42041465/6214440 As a side note. Once you have the NDK unpacked and the paths set, the installer will show it as shown in the screenshots. Hope it helps. Regards

The image upload is currently broken, I can't see the image. Do you have anything in the Compilers panel in Build and Run ?

Since this week i have no problems. Maybe an Windows update.

thanks It was very good tips

@koahnig said in set<int> in Qt creator and debugger: E.g. are there conflicts through the various files holding settings? There might be, you will probably at least need to reconfigure the project's kits (i.e. deleting the *.pro.user files). I'd try to load them directly first though, it might work fine. @koahnig said in set<int> in Qt creator and debugger: The same problem there. It's the same data structure, so no surprise at all, indeed.

Hi, I'd recommend starting by the port to Qt 4 by completely forgetting that there's a compatibility module. This one was only there to help transition but it's not available in Qt 5 so there's no reasons to try to use it. Then just try building the your project with Qt 4. If there are classes missing, check the porting guide to see with what to replace them. If your big project contains several sub-projects, then just build them one after the other so you'll have less stuff to handle at once. Once thing you can do while going through your sources is to remove the modules from the includes e.g. from #include <QtGui/QWidget> to #include <QWidget> that will save you some time for the Qt 4 to Qt 5 transition.