Skip to content

Qt Creator and other tools

Have a question about Qt Creator, our cross-platform IDE, or any of the other tools? Ask here!
7.4k Topics 34.5k Posts
  • 0 Votes
    5 Posts
    9k Views
    C

    http://bugreports.qt.nokia.com/browse/QTBUG-18985

    Which I filed yesterday,
    May also be of interest too. It relates to whats causing the issue and 3 or so things that may be done to fix this.

  • QT VS Addin and Visual Studio 2010

    1
    0 Votes
    1 Posts
    4k Views
    No one has replied
  • Adding classes to a VS2008 project

    3
    0 Votes
    3 Posts
    2k Views
    A

    Thanks for the quick reply. I seem to have resolved this issue (it can now find the files and I'm not sure what I did to fix it) but they are not being moc'ed so the link fails. I have seen the resolution to this problem when using a qmake file but I don't have one. How do I ensure that the new .cpp/.h files are moc'ed.

    Thanks,
    Andy

  • Phonon: edit audio file meta data

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • Build a project without QT libs and include

    9
    0 Votes
    9 Posts
    4k Views
    G

    It supports the MS c++ tool chain (like cl, link, nmake, ...) :-)
    MSVS is the IDE itself :-)

    If he does not beleive, he should test it, but then also create the project like the users would do, mith MSVS :-)

  • 0 Votes
    5 Posts
    5k Views
    G

    Hi andreaplanet,

    the specfiles are not specifically to cross compiling, they are specific for the cimpiler. And there are many examples, all in the file structure.

    And regarding an example, which one? host linux, windows or mac? Which compiler to use for the target environment? All this depends on the host and target environment, and each compiler might be different. How to do cross compiling is just a thing of the toolchain, and so it heavily depends on that.

    Giving an example with Linux (perhaps Suse enterprise) and chroot mechanism would fulfill linux, what with mac and windows? So I think, it's ok how it is. It could be something for the wiki here, if someopne writes something for a specific environment and toolchain.

  • Designer

    7
    0 Votes
    7 Posts
    3k Views
    T

    You can check Qt Creator for an example. It embeds the designer.

  • 0 Votes
    6 Posts
    4k Views
    T

    Please file a "bug report":http://bugreports.qt.nokia.com/ if something crashes!

    This is especially if you can provide good information on how to reproduce the issue and/or a backtrace. In case of a debugger issue the debugger log (top right in the debugger view) is absolutely necessary for us to find the issue, too, so please also include that.

    Looking forward to your report!

  • 0 Votes
    6 Posts
    3k Views
    mzimmersM

    Done.

    "link to bug report":http://bugreports.qt.nokia.com/browse/QTCREATORBUG-4593

  • 0 Votes
    2 Posts
    3k Views
    V

    For designer you can use the signal and slot editor, but not to connect with other widgets/dialogs.

    You better can use creator for this task, then you can 'talk' with any object in your project as long as you use slots or make functions public.
    In code use connect.

    edit:
    look "here":http://developer.qt.nokia.com/forums/viewthread/5273/#31552 to

  • Messed up UI under Ubuntu

    24
    0 Votes
    24 Posts
    9k Views
    H

    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).

  • 0 Votes
    11 Posts
    4k Views
    S

    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?

  • Tip: 'Enclose in QLatin1String'

    6
    0 Votes
    6 Posts
    3k Views
    M

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

  • 0 Votes
    5 Posts
    3k Views
    E

    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.

  • 0 Votes
    6 Posts
    4k Views
    T

    Didn't know we did that;-)

  • 0 Votes
    16 Posts
    12k Views
    ?

    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...

    --

  • 0 Votes
    3 Posts
    2k Views
    L

    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/

  • 0 Votes
    5 Posts
    3k Views
    W

    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.

  • Qt creator 2.1.0 discussion.

    2
    0 Votes
    2 Posts
    2k Views
    S

    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.

  • 0 Votes
    2 Posts
    5k Views
    T

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