Qt Creator and other tools

I also thought I was experiencing an issue with the glibc toolchain, but our resident toolchain guru set me straight. We quickly built up the "strace" tool and added that to our embedded system. It immediately told us there was a library dependency that was not being met (libQtOpenGL in our case). This may not be your issue, but I wanted to share how we dissected the error to identify the root cause.
Good Luck!

I am having almost the same problem, any updates on the issue? I started believing this is a bug in OpenCV that has something to do with Qt.

I think the application output window does not even accept input at all. So far I always tested this with embedded devices that come with their own input methods... I doubt anybody ever wanted stdin redirection so far.

Please consider to "file a bug report":http://bugreports.qt.nokia.com/ .

Sorry to say that but qt style guide and qt creator style guide are equal in that particular case.

I got it now. I should use Qt Creator and try Qt Tutorials.

Thank you my friends for help.

In my opinion this is not a qdoc problem but a problem with your code.

If you write (just for explanation)

@ static const int dirEsquerdaCima = 1;
@

on top of a *.cpp or *.c module (file) then this means, that this variable is only known within that c or cpp module. You can write that code into evey module you want so every module will have its own variable - each not visible from the other modules.

This is what you do, when you write that code into a header file. Each module that includes this header file will have its own variable.

But if you write

@ extern const int dirEsquerdaCima;
@

in the mentioned headerfile and

@ const int dirEsquerdaCima = 1;
@

in ONE of your modules it probably will work. This idea does not cover static variables in classes.

PLease note, that qdoc is an internal Qt documentation generator and is not intended for general use. Qt devs usually recommend using doxygen.

If you insist on using qdoc, take a look at Qt sources to see how contributors do it.

FWIW, I have revisited this issue since I really didn't like having to hard set QT_QMAKE_EXECUTABLE. So, instead, I rely on the fact that I, personally at least, set Qt's path in /etc/profile:

@EXECUTE_PROCESS(
COMMAND sh -c ". /etc/profile && which qmake"
OUTPUT_STRIP_TRAILING_WHITESPACE
OUTPUT_VARIABLE QT_QMAKE_EXECUTABLE
)@

When you got the SIGSEGV while debugging, click away the debugger message box and look at the stack with the call history. There you'll find the procedure that was last called (as JKSH wrote).

My Qt Creator is 2.4.1.My step is as default.Now I create an empty project and compile the code,it works well.

Press Shift-F11 to run until a function exits. The return value will show up in a separate section in the "Locals and Expressions" view.

Pure console stuff on Windows? Put a sleep(1) or equivalent at the top of main()

Gdb 6.8 is indeed not supported with Creator 2.5. On Mac, use some of Apple's 6.3 fork, and everywhere else, Python scripting is required. The official lower limit is 7.2 IIRC.

Hey coolhead, could you give us a tip how you have converted the html files using qhelpgenerator. I have a bunch of htmls that i want to combine in one qhc file. Please help

Got it, PEBKAC.

You were close to right with the problem, franku.

Thanks for the replies, appreciate the help.

Please file a bug report then, providing as much information as possible on how to trigger this behavior.

Thanks a lot, I agree with your suggestion

Hello Everyone:

I am struggling to get debugging working, and I feel quite "in the dark" about its setup.

I had the errors that began this thread. I tried everything in this thread and finally made progress by following Uranium-235's checklist.

I don't understand cloning, but at least I was able to run the debugger without errors. However, all of my breakpoints are ignored!

There is much that I don't understand about Tools->Options->Debugger:

Do I need to add something to the Source Path, or the Target Path, in the General sheet?

In these sheets, what does it mean that there are a bunch of items in a list? Are they all accessed, or do I have to specify the use of one, somehow?

In the CDB sheet, I added the CDB location folder in Source paths. Should I add something to Symbols paths? There are three paths specified currently, I don't know why.

There are many items listed in Options->Build & Run-> Tool Chains, (including the clone I made). Is it no problem to have so many items? Should I somehow indicate a priority?

Background: I inherited a large Qt project. It was created on a different computer; I downloaded Qt 4.8.1 for Desktop - MSVC2010 (Qt SKD).

Thanks!