Qt Creator and other tools

I'm starting to appreciate Fedora too. Everything Qt related seems to work out of the box. I even managed to build the postgresql driver (64 bit) easily (I had a similar post with my troubles building it under Windows x64).

Then it have to be a bug as it is clearly there in the beta and I haven't install it ... but it seems to be gone in the latest snapshot. In my opinion it isn't needed to be reported. Do you think otherwise?

Andre: Thanks for the link to the conversation, good read.

My account does not allow to log into the bug report area. Below is the Debug logger produced using QT Creator 2.1.0 --> Starting debugger 'CdbEngine' for tool chain 'Microsoft Visual C++'... dDebugger settings: dUseAlternatingRowColours: false (default: false) dUseMessageBoxForSignals: true (default: true) dAutoQuit: false (default: false) dLogTimeStamps: false (default: false) dVerboseLog: false (default: false) dCloseBuffersOnExit: false (default: false) dSwitchModeOnExit: false (default: false) dUseDebuggingHelper: true (default: true) dUseCustomDebuggingHelperLocation: false (default: false) dCustomDebuggingHelperLocation: (default: ) dDebugDebuggingHelpers: false (default: false) dUseCodeModel: true (default: true) dUseToolTips: false (default: false) dUseToolTipsInLocalsView: false (default: false) dUseToolTipsInBreakpointsView: false (default: false) dUseAddressInBreakpointsView: false (default: false) dUseAddressInStackView: false (default: false) dRegisterForPostMortem: false (default: false) dEnvironment: (default: ) dScriptFile: (default: ) dWatchdogTimeout: 20 (default: 20) dMaximalStackDepth: 20 (default: 20) dShowStandardNamespace: true (default: true) dShowQtNamespace: true (default: true) dSortStructMembers: true (default: true) dAutoDerefPointers: true (default: true) dListSourceFiles: false (default: false) dSkipKnownFrames: false (default: false) dEnableReverseDebugging: false (default: false) dAllPluginBreakpoints: true (default: true) dSelectedPluginBreakpoints: false (default: false) dAdjustBreakpointLocations: true (default: true) dNoPluginBreakpoints: false (default: false) dSelectedPluginBreakpointsPattern: .* (default: .*) dBreakOnThrow: false (default: false) dBreakOnCatch: false (default: false) dState changed from DebuggerNotReady(0) to EngineSetupRequested(1). dVersion: 6.12 dNOTE: ENGINE SETUP OK dState changed from EngineSetupRequested(1) to EngineSetupOk(3). dQUEUE: SETUP INFERIOR dCALL: SETUP INFERIOR dState changed from EngineSetupOk(3) to InferiorSetupRequested(4). dNOTE: INFERIOR SETUP OK dState changed from InferiorSetupRequested(4) to EngineRunRequested(6). dQUEUE: RUN ENGINE dCALL: RUN ENGINE Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. CommandLine: "C:\Documents and Settings\joe.elvin\My Documents\Qt Projects\untitled\debug\untitled.exe" Starting directory: C:\Documents and Settings\joe.elvin\My Documents\Qt Projects\untitled dNOTE: ENGINE RUN AND INFERIOR STOP OK dState changed from EngineRunRequested(6) to InferiorStopRequested(12). dNOTE: INFERIOR STOP OK dState changed from InferiorStopRequested(12) to InferiorStopOk(13). dNOTE: INFERIOR RUN REQUESTED dState changed from InferiorStopOk(13) to InferiorRunRequested(9). dNOTE: INFERIOR RUN OK dState changed from InferiorRunRequested(9) to InferiorRunOk(10). Symbol search path is: symsrvsymsrv.dllC:\DOCUME~1\JOE~1.ELV\LOCALS~1\Temp\symbolcache*http://msdl.microsoft.com/download/symbols Executable search path is: C:\Documents and Settings\joe.elvin\My Documents\Qt Projects\untitled\debug ModLoad: 00400000 0040a000 untitled.exe ModLoad: 7c900000 7c9b2000 ntdll.dll ModLoad: 7c800000 7c8f6000 C:\WINDOWS\system32\kernel32.dll sLoading the custom dumper library 'C:\Qt\4.7.2\qtc-debugging-helper\debug\gdbmacros.dll' (injection) ... ModLoad: 67000000 673f4000 C:\Qt\4.7.2\bin\QtCored4.dll ModLoad: 7e410000 7e4a1000 C:\WINDOWS\system32\USER32.dll ModLoad: 77f10000 77f59000 C:\WINDOWS\system32\GDI32.dll ModLoad: 774e0000 7761e000 C:\WINDOWS\system32\ole32.dll ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll ModLoad: 77e70000 77f03000 C:\WINDOWS\system32\RPCRT4.dll ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll ModLoad: 71ab0000 71ac7000 C:\WINDOWS\system32\WS2_32.dll ModLoad: 71aa0000 71aa8000 C:\WINDOWS\system32\WS2HELP.dll ModLoad: 10480000 10557000 C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_5d84dd2f\MSVCP90D.dll ModLoad: 10200000 10324000 C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_5d84dd2f\MSVCR90D.dll ModLoad: 76390000 763ad000 C:\WINDOWS\system32\IMM32.DLL w*** WARNING: Unable to verify checksum for wC:\WINDOWS\system32\wxvault.dll w w ModLoad: 10000000 10063000 C:\WINDOWS\system32\wxvault.dll ModLoad: 76bf0000 76bfb000 C:\WINDOWS\system32\PSAPI.DLL ModLoad: 71b20000 71b32000 C:\WINDOWS\system32\MPR.dll ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.dll ModLoad: 77f60000 77fd6000 C:\WINDOWS\system32\SHLWAPI.dll Exception at 0x7c919af2, code: 0xc0000005: write access violation at: 0x10, flags=0x0 Exception at 0x7c919af2, code: 0xc0000005: write access violation at: 0x10, flags=0x0 dDisabling dumpers due to debuggee crash... dNOTE: INFERIOR SPONTANEOUES STOP dState changed from InferiorRunOk(10) to InferiorStopOk(13). dStopped, current thread: 0 sStopped at 2089917170 (RtlpWaitForCriticalSection) in thread 0 (missing debug information). sException at 0x7c919af2, code: 0xc0000005: write access violation at: 0x10, flags=0x0 s s w*** WARNING: Unable to verify checksum for wC:\WINDOWS\system32\detoured.dll w w ModLoad: 00380000 00385000 C:\WINDOWS\system32\detoured.dll ModLoad: 7c9c0000 7d1d7000 C:\WINDOWS\system32\SHELL32.dll (10f8.148c): Access violation code c0000005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled.

Didn't know we did that;-)

Mmm.... my approach to this would be using DDD (data display debugger? or sth like it) as an interface to GDB, then setting some breakpoints... --

Thanks secretNinja. Qt Creator 2.1.83 (unstable) has the external tools feature. Very cool. If anyone else needs it, here's a link to "download Qt Creator unstable versions.":http://get.qt.nokia.com/qtcreator/snapshots/

OK, this error is now fixed having upgraded to the latest Intel Compiler (12.0.3.175), and for what it's worth build took 48 minutes using jom and 4 cores. Now off to see if I can get a 64 bit build of Creator done.

Isn't it time to discuss "QtCreator 2.2":http://labs.qt.nokia.com/2011/03/24/qt-creator-2-2-beta-release/ ... yes, it is beta but I haven't found any serious issues so far ( on the other side - I haven't used it so much ). I found QtCreator several months ago ... and I couldn't understand how it was possibly to live without it for so long :) And adding new features like "Qml Perfomance Monitor":http://labs.qt.nokia.com/2011/04/07/qml-perfomance-monitor/ is great.

There is a bug report about this: http://bugreports.qt.nokia.com/browse/QTCREATORBUG-4437

Ask on IRC on the #qt-creator channel; all in all, creator knows how to nicely show Qt datatypes, therefore there must be a way to do that with arbitrary datatypes. Apart from this, use a typedef, not a define :)

[quote author="Raul" date="1302092643"]I've been meaning to learn Qt Quick but where do I start? [/quote] Try here: http://developer.qt.nokia.com/wiki/Qt_Quick :)

This 'issue' appears to have been caused by an aborted build of the SDK under a different target platform and was 'fixed' as a result of a rebuild of the SDK. -- William

"There are no issues with the tool chain support" :-) Maybe an unfortunate choice of words.. But if I have a build issue I would be inclined to post here first in case it is 'driver' error. For what it is worth the ONLY compiler we can use is Intel so I may be back! -- William

you can use the tools outside creator. Some of the comercial windows tools are also not integrated inot MSVS but can be used with MSVS binaries.

Do Qt creator have related analysis tool? If Qt creator have some analysis, could you introduce them to me?

Thank you both for your advice. Finally I have found a way of moving on without using the FLTK libraries, and it seems to work fine. See you around. Miguel

Thank you very much, it works indeed. What was confusing me is that @message ($(FOO))@ outputs @Project Message: <foo content>@

We had a similar issue with templates, which are somehow C++ macros (just better or worse, depending if you write them or have to understand the ones of another developper....) One of the solution we had was to define virtual interface for our slots, and then, have our real class derivate from interface and qobject, just redefining the previous virtual functions as slots. The fun thing is you can do the connect from your interface as it's done on runtime. Kind of risky however to maintain, so we finished by generating these aprts of code with some external python scripting.

Maybe I am pointing out the obvious but have you logged out (rebooted even) after setting your QTDIR env parameter? Also it may not do any harm to modify your paths to have a single \ even better is to change them for /. For what it's worth. -- William