Qt Creator and other tools

Oooooh, before trying to build/generate the qvfb tool by myself, I forgot to choose the Qt lib I just built... So I entered again in the Qt Creator to update the qvfb ".pro" project by setting reference to the correct Qt lib (the one I built by myself), changing the default reference value "QT in path" by the "4.7.1" one, which, I guess, was the one corresponding to what I just built before... Then trying to rebuild qvfb goes farther but stops again with a new compiling error (argggh... !?), complaining about one more missing "X11/extensions/XTest.h" include file...
Well I looked around the web with Google and I found that "XTest.h" was belonging to "libxtst" which I guess was not installed by default on my Fedora 14 system... So I did a "yum search libxtst" to look for exact package/component name for "libxtst" on my Fedora 14 system,
and then, I decided to install
libXtst.x86_64 : X.Org X11 libXtst runtime library
and
libXtst-devel.x86_64 : X.Org X11 libXtst development package:

as root:

yum install libXtst.x86_64 libXtst-devel.x86_64

As a result, I succesfully regenerated the binary executable file for qvfb tool... Great !

:-)

Alain-Pierre

The actual definition of Q_EXPORT_PLUGIN2 depends on the value of QT_STATICPLUGIN. One of these uses the value of PLUGIN.

you should've looked at how the Qt sources are organized to find it out by yourself :)
Tobias is our Creator Guru :D

Thank you very much!!!

I already set-up remote compiler. My questions was to have clear in mind that this is the same (remote compiling with linux) as the symbian compiling under windows. As a matter of fact I have no great problems to use one platform or another, but I prefer linux.

Using the simulator in ubuntu, how this can be considered near to a "real" symbian development ?

Thks

NetBeans IDE also uses command line svn, and it works correctly, if I set the proxy within that IDE.

If it is not possible, so I need to find a way how to set the proxy for svn tool then.

[quote author="Tobias Hunger" date="1298224767"]How am I supposed to understand that last comment? Did you cross-compile Qt Creator for Windows on a Linux box? The Linux version of Qt Creator we ship is build with gcc, not mingw... that is why I am confused:-) [/quote]

Sorry let me clarify...

I have a dual boot machine, Kubuntu Linux and Windows 7.

In Linux downloaded from the repositories.
In windows, I downloaded from the Qt web site.

The windows version of Qt Creator was compiled with Visual Studio, but ships with Mingw. So when you attempt to create your own plugin, the plugin will not load with a message of:

Expected build key “Windows msvc release full-config” got “Windows mingw release full-config”

So I tried (on windows) to download the QtCreator source and compile with Mingw, but I am getting the errors mentioned in the original post.

All I was saying is that custom plugins work perfectly in Linux because QtCreator was compiled with the same compiler, Windows however is compiled with VS, and QTCreator uses a different compiler, so plugins will not load.

Is there a way to bypass the plugin signature checking without a compiling QtCreator? (Perhaps a argument or option I missed?)

Here's a little test .pro:
@CONFIG(debug) {
message(debug)
}
CONFIG(release) {
message(release)
}
CONFIG(debug, debug|release) {
message("debug, debug|release")
}
CONFIG(release, debug|release) {
message("release, debug|release")
}
@

With the outputs:
@$ qmake
Project MESSAGE: debug
Project MESSAGE: release
Project MESSAGE: debug, debug|release

$ qmake CONFIG-=release CONFIG+=debug
Project MESSAGE: debug
Project MESSAGE: debug, debug|release

$ qmake CONFIG-=release CONFIG-=debug

$ qmake CONFIG+=release CONFIG-=debug
Project MESSAGE: release
Project MESSAGE: release, debug|release
@
The second parameter seems to be which configuration options to check for. If I change the last check into
@CONFIG(release, debug|unrelease) {
message("release, debug|release")
}@

@$ qmake CONFIG+= release CONFIG-=debug
Project MESSAGE: release
@

If I change the check into
@CONFIG(release, release) {
message("release, debug|release")
}@

I get
@$ qmake CONFIG+=release CONFIG+=debug
Project MESSAGE: debug
Project MESSAGE: release
Project MESSAGE: debug, debug|release
Project MESSAGE: release, debug|release
@

Besides specifying the items to check for, some seem to take precedence. I'm not all too sure how this is determined. Anyway, I hope this at least clarifies something.

[quote author="Volker" date="1298236788"]sigh...[/quote]

Sorry, if you have the rights, you can close this post.

You are aware that Qt Creator is open source? So if you want to develop something like it, maybe you can get away with programming plugins for it? ;-)

Qt Creator is actually mostly a plugin manager. Almost all the functionality is provided by plugins. So if you remove all our plugins you get a pretty basic shell to add you own plugins into.

Great to hear. Thanks.

exactly

Maybe "this":http://gitorious.org/qt-creator-todo-plugin/qt-creator-todo-plugin will do all work for you? :)

@Darryl, Could you point me to the directory containing the lib files. I installed Qt to C:\Qt....

[quote author="VickyB" date="1297935126"]Sorry for an OT! I wish to use QT Creator, that's why!
[/quote]

Still offtopic. Write your code, setup a project (probably plain Makefile or CMake, as qmake seems not so appropriate) and go ahead.

If you have specific questions on how to work with Creator, we'll try to answer. But please ask in the correct forum then - this much time to look for the correct place should be spent, don't just use the very first forum you see. Thanks.

I saw it, but the answers were not complete. ;-)

[quote author="Franzk" date="1297761812"]wild, LiamMaru & Darryl: Perhaps it is time then to suggest some improvements to the general work flow of designer?[/quote]

I could, but if you read my post you should have realised it was very much a 'to each is their own' line of commentary. I'd rather leave suggesting improvements to those who either use or have future intention to use Designer.

Thanks for reporting.

For those interested, the issue can be tracked here: http://bugreports.qt.nokia.com/browse/QTCREATORBUG-3789

Hi,

Thanks a lot! That worked perfectly :) I had assumed adding the headers to the sources variable would confuse cmake (thought it might try to compile the headers) but both cmake and qtcreator do the right thing.

Any clues about the second point? I'm really addicted to auto-completion :P

Thanks again,
Miguel S.

The reason why you get three messages is the following: qmake goes through three stages when generating the Makefile(s) for your project. Once for debug, release and the metamakefile.

See the description of debug_and_release and build_pass here http://doc.qt.nokia.com/4.7/qmake-variable-reference.html#config for more insight.

Yes its true. :)

http://doc.qt.nokia.com/4.7/qmake-advanced-usage.html#scopes

We're currently investigating. Nothing concrete yet.

I tried to recompile qt creator (2.0.1) but still it doesn't work.
I will try building UI on designer and then integrating it on creator.