Qt Creator and other tools

I might be wrong, since I am not a Troll nor from Digia. However, I looks to me like the vsaddin is completely open source. It is supplied by Digia, but as far as I remember it is not part of the license. Therefore, I would assume that this is not on their roadmap at all IMHO. Probably you should address this question directly to Digia.

Thanks for the hint. The command line invocation uses env variables (LD_LIBRARY_PATH in my case) and app found a library in /usr/bin64. QT Creator has different settings and used different version of the library for linking.

Glad that I could help!

My problem with CDB using MSVC is solved. Turns out it's a pretty common problem, not at all related to Qt. It's caused by the existence of pre-existing Visual C++ redistributables. The installation works perfectly (in my case) after they are uninstalled. There are loads of pages that describe the many causes and solutions, but this one seems to be the clearest: http://notepad.patheticcockroach.com/1666/installing-visual-c-2010-and-windows-sdk-for-windows-7-offline-installer-and-installation-troubleshooting/ Hope this helps others who may be suffering from the same problem.

Here is the link to my bug report: https://bugreports.qt-project.org/browse/QTCREATORBUG-7147

It is unlikely to be changed, but if it isn't documented there is most probably no guarantee. But one should mention that <code>#include <...></code> and <code>#include "..."</code> behaves exactly the same, except that <code>"..."</code> looks in the current directory first, then in global directories. From the technical point of view there is no need to use the <code><...></code> notation just to include global files.

That's right, Scylla! Thanks a lot :)

Oh sorry guys for this very late reply. I found out that I tried to use 64-bit library with 32-bit compiler. Such a shame :D haha Thank you all very much for the replies. I do appreciate your help.

Hm, sorry, I never got my fingers on translating a QML file, so I cannot comment on that. Hopefully someone else can jump in here.

You can try a "hard reset" by uninstalling the SDK, sensibly deleting % APPDATA %/Nokia, HKCU/Software/Nokia, HKCU/Software/Trolltech, HKLM/Software/Nokia, HKLM/Software/Trolltech and reinstalling the SDK and Qt Creator.

Dropping MinGW mean the developers have to download VC++ express (at least), Qt Creator and Qt toolkit ... this is really exhausted process (as you know Microsoft prevents VC++ redistribution). PS I was so glad when Nokia created QtSDK all-in-one distro.

Yes, it is a bit different from how integrated unit testing is with Java/.NET etc., but I do not think it is that unproductive. The primary target in each of my IDE sessions is the test project. I add code to my library project, add unit test code to the test project and just hit run. Since the library project is marked as a dependency of the test project, it automatically builds the library and then builds and executes the tests. The end result is you get most of the same type of integration as with Java/.NET

1 screen, 1 keyboard, 1 mouse but several PC's in a different location.

Thanks, I forget about time, but this works outside Qt Creator. There is a another solution, which will work inside Qt Creator?

qmake supports the inclusion of other project files using the include() statement. @ // common.pri SOURCES += commonFileA.cpp commonFileB.cpp commonFileC.cpp HEADERS += commonFileA.h commonFileB.h commonFileC.h // projectA.pro TEMPLATE = app include(common.pri) SOURCES += projectFileA.cpp HEADERS += projectFileA.h // projectB.pro TEMPLATE = app include(common.pri) SOURCES += projectFileB.cpp HEADERS += projectFileB.h @ You can even combine both projects to a single project using the subdirs template (given the .pro files are in projectA/projectA.pro and projectB/projectB.pro). @ // project.pro TEMPLATE = subdirs SUBDIRS = projectA projectB @