Qt Creator and other tools

Thanks for the reply.

bq. lijo: There are a couple of limitations to your approach:

This requires tests to run as part of the build system (otherwise the compiler output parsers are not active)

For me running unit tests after each build is more important. If this happens smoothly, I would not have to run the unit tests manually at all.

bq.

This assumes a GCC based compiler, MSVC, Clang and others have very different output formats

I think any one who has access to the unit test framework source code can easily tweak its output to their compiler specified format.

Event though limited, this approach works very well for my purpose as of now. If I get into any trouble with that, I will definitely check out tasklist :-)

Ok, I guess I got it after looking through the sources of the installer framework. THe additional repo settings are for using another repo with the same packages (not additional), e.g. if the main server is down.

So I'l try to create my own installer with Qt already included.

Thx anyway.

@steveking, My Qt version is : 4.8.0 if this also helps

sorry

Just a quick not to say that I found the segfault source. Another change since the tutorial was written meant that I was not calling setWidget() in the IEditor instance. As a result, the widget was being returned as 0, resulting, as might be expected, in a SegFault.

Thanks again... until the next problem.

I opened the bug report. Yes, The Makefile.am contains the header file names.

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

These "defines" are set in the qmake mkspecs. You find them in the mkspecs directory in your Qt installation. I'm not sure whether some of them are hard coded in the qmake binary. You'll need to dig around yourself a bit here.

You are welcome.
However, I did not mean to drag you away from using msvc as tool chain. However, my feel is it might be a tedious thing to get it go, so I have avoided so far.
If you have a licensed version of msvc you may want to use also the IDE of msvc together Qt. However, an express version will not do, since it is probably better also to use vsaddin which requires a full version of msvc.

We have no way to know that.

Only you can debug your code and look for that mistake where you try to get an value from an index that is not in your list (like if you have a QList with 10 elements the valid indexes will be between [0] and [9])
And be extra careful if your list is shared between threads - you can take the size of the list in a thread, but if the access to the list is not properly locked another thread can remove elements from the list and then the first thread will try to access invalid indexes.

My application is compiled with mingw - same as it was with creator 4
But I cannot debug!!
anything else I can try?

Yes, our plugin documentation is rather outdated. Qt Creator changes rather fast and since we do not promise any kind of compatibility we don't bother to document too much either to avoid the impression that any of the APIs we use internally are stable to any degree.

So how can you find your way around? I am afraid there is no way around reading a lot of source code and/or asking on IRC (#qt-creator on the freenode network) or the mailing list. Code navigation in creator also helps: Just type "Ctrl-K" and then type "c TextEditor" to open the TextEditor class. There is little need to know where the file is actually located.

The GLSLEditorEditable class as well as the QmlJSEditorEditable are most likely good places to get started (found those by pressing "Ctrl-Shift-T" on the BaseTextEditor class) as those are real editors but less complex than the C++ one. I never really worked with the editor code though, so I can be wrong:-)

Note that in the vast majority of cases, your code will have the same memory leaks on Linux, Mac or Windows (aka as "the ones you put in" :-) ). For performance there may be differences.

Apologies - I am working on a wxWidgets project (using the autotools plugin in Qt Creator). So they are xrc files indeed. But no worries - I found the xrcEd tool to modify them independently.

I think it is the remote target file system on the host. So if you have the remote target's file system on your host, (I have this set up using NFS server so my embedded linux device uses the file system on my linux host) then I think that is what you use for Sysroot.

And what is the Sysroot ?

Yes, I dont use remote debugging on QT.