Qt Creator and other tools

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
@

[quote author="kwyjibo" date="1331163269"]Anyone? I don't want to cancel the use of Qt just because their IDE can't import a simple library[/quote]

That's a pretty bold statement. I wouldn't chalk up the fact that you're having problems as "their IDE can't import a simple library." Thousands of developers write millions of lines of code every day using the IDE, and I haven't heard of library importing being a huge stumbling block. Typically it works very well.

On a more helpful track, though, do you know for sure if the $$PWD refers to your untitled/ directory at build-time? or if it refers to untitled-build-desktop-* ? (I don't remember the semantics of it offhand.) You might try turning off shadow build in your project preferences, to see if that makes a difference.

Hopefully this will be helpful: I tried installing the Microsoft Debugging Tools and it didn't work. I tried to look up the installation and found that the installer had only copied .msi files to my hard drive. After running the .msi it worked.

I bit strange since my expectation of an installer is that it actually installs software.

OK, thank you. Marked as solved.

I'm 99% sure he just downloaded the Windows binary. I'll double check today.

I wonder if it had something to do with the name of the directory he installed it in...I sort of remember something about MinGW not liking directories with spaces in their names.

Posted a bug report:

https://bugreports.qt-project.org/browse/QTCREATORBUG-7044

PS:

bq. If you double click on a .ui file it opens in designer mode by default. If you don’t close it with ctrl-w, but just hit ESC, you’re in a plain text editor with the XML too.

Not an editor. Just a viewer. I can't change anything there.

Thanks Tobias,
the "Adding New Custom Wizards":http://doc.qt.nokia.com/qtcreator-2.4/creator-project-wizards.html page is exactly what I was looking for.

Moreover, I was looking it exactly for this reason: "If you have a team working on a large application or several applications, you might want to standardize the way the team members create projects and classes." (excerpt taken from the mentioned page). I have to write a few strongly-related applications and I hoped to find a way to standardize the development process.

Most likely, I will just use templates. In any case, the possibility to use generator scripts is an interesting plus.

I'm not going to build binaries for new (different) platforms so I'm not going to touch the mkspecs files (at least, not for now).

BTW: qmake is fine for me, at least for the moment. For more complex needs, I already had a look at cmake, scons and qbs. I will not run out of alternatives... :-)

Your new Qt Build System (qbs) seems to be very smart and very promising. Thanks for having developed it (even if, maybe, a new build system was not the most urgent need of Qt...).

Thanks again.

Please file a "bug report":http://bugreports.qt-project.org/ against Qt Creator. Please attach the debugger log, without it it is really hard to diagnose any debugger related issue. Thanks!