Qt Creator and other tools

I've created a "bugreport":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-4249

"Qt Creator -> Preferences (or shortcut cmd-comma) -> Qt4" is the menu path for that in OS X version.

I don' know, but the bug can reproduce every time Open designer(zh_CN version4.7.0), drag and drop one form(must need qrc file ) to window. Now pop up a messagebox: "loading qrc file". Then if I clicked "Yes" button, the window crash., or if I switch other windows, the messagebox not respose, must kill it in "windows Task Manager". So this problem I met is not the same to "Multiple pages in QStackedWidget":http://developer.qt.nokia.com/forums/viewthread/4293. If not loading qrc file, I can open more than 15 files

Better file a bug report on http://bugreports.qt.nokia.com

bhupathirao: Please check the documentation we ship with Qt Creator: That does explain all these details. The Deployment settings are in Project mode, Run Settings.

Thanks for all the suggestions. This is going to be just me (or predominantly me, anyway). Those services that Volker mentioned sound good, but...I'll have to schedule some time to learn them. I guess it'll wait until I've become more proficient with Qt.

Never mind, classic case of me spotting the problem a few seconds after posting the issue. Auto complete seems to have messed up the class name in the test class implementation file. Sorry for wasting bandwidth.

Ah, ok, so it is the right site. I found it but seeing the text-only pages I thought that it was a wrong link. It seems that these pages have no stylesheet on them at all... I try later. Thanks.

I'm getting crazy trying to make it work the way I think it should. I must be misunderstanding something. I would like to have qmake generate makefiles that produce the output (TARGET) in specific directories for debug and release. I've tried something on the lines of what you (and many others) suggest, but it simply doesn't work for me. I have: @TEMPLATE = lib CONFIG = qt shared debug_and_release build_all debug_and_release:build_pass { CONFIG(debug, debug|release) { TARGET = ColorAnalyzerSimulator_debug DESTDIR = debug } else { TARGET = ColorAnalyzerSimulator_release DESTDIR = release } } DEPENDPATH += . INCLUDEPATH += . Input HEADERS += ColorAnalyzerSimulator.h SOURCES += ColorAnalyzerSimulator.cpp@ And I issue the command @qmake -spec macx-g++ -o Makefile.mac Simulator.pro@ and when I look into the Makefile.mac.Debug, TARGET has the default name (Simulator) and DESTDIR is empty!! I have tried many variations of these settings but no result. I've also tried a similar thing on Linux and still no result. I really hope someone can help. [quote author="GordonSchumacher" date="1292262276"]Honestly, you really don't want OBJECTS_DIR to be the same between the builds either! (What happens if you inadvertently get a mixture of debug and release object files...?) What I've done in the past is something like: @debug_and_release:build_pass { CONFIG(debug, debug|release) { CURBUILD = debug } else { CURBUILD = release } DESTDIR = $${OUT_PWD}/$${CURBUILD} OBJECTS_DIR = $${OUT_PWD}/$${CURBUILD}/$$dirname($${_PRO_FILE_PWD_}) MOC_DIR = $${OBJECTS_DIR} UI_DIR = $${OBJECTS_DIR} RCC_DIR = $${OBJECTS_DIR} INCLUDEPATH += $${OBJECTS_DIR} LIBS += -L$${DESTDIR} unset(CURBUILD) }@ I'm not positive those are all actually necessary, but you get the idea anyway.[/quote]

The default debug flags are simply "-g" which is set for QMAKE_CFLAGS_DEBUG and QMAKE_CXXFLAGS_DEBUG.

You have to call qmake -set separate as single command and not in combination with other options.

OK, my mistake... Even if I checked lots of things before posting here, I overlook a #undef _DEBUG somewhere in an included header file. Thanks for your help

The nightly builds are currently using the 2.2 branch as far as I know. So that should be a fast way to test the branch. It is not beta-release ready at this time, but it is rather stable already and the version most of us currently use to develop Qt Creator in.

[quote author="tbrowder" date="1300200176"]Andre and Volker, that may be similar to the problem I reported: the output from Creator is chopping the compiler command options and causing a make error, which could reflect a compiler exception since it is an unknown command to g++.[/quote] Can you create a small sample project to demonstrate the effect? Also, what's the command line which Creator calls on qmake? You can see it in the output tab of Creator.

It was only an example, and in effect I had some difficult to find this link. It's on the versions listed under qt developer forum and not the primary forum.nokia.com I saw that in this there are now only the last sdk versions. But It was necessary to show the right example to that guy. As a matter of fact, I save a local backup of all the versions of os and dev environments I download (that I find useful). So if the things changes I have a local history almost to remember my path.

what settings does it show in the "Projects" mode

Oh, OK...that's pretty slick. I think I'll delete my existing project and start over, with the files sorted into directories. Thanks.

Some of the C++0x features have made into to gcc/mingw. I am not sure nested right brackets is allowed but I used auto a lot until I find out Mac is stuck in the last century thanks to Apple. I really hope LLVM/clang support in Qt is coming quickly. A common compiler target makes life a lot easier.

after a few hours, i finally found the my error. my .pri file was correct. example .pri file SOURCES += source1.cpp source2.cpp source3.cpp example1.pro should have something in it like this but i forgot the '+' SOURCES += example1.cpp

Thank you very much, it worked with: @sudo chown -R user /home<user>/.config/Nokia@