Qt Creator and other tools

I agree with Leandro closing the feature request: That is too intrusive to implement for very little gain.

But I do think that you have a valid point there, so I opened "another feature request":https://bugreports.qt.nokia.com/browse/QTSDK-1121 with our Qt SDK team to install the headers read-only by default. I hope that is OK with you.

So, I think I found out what is going on. The reason I got this message was because I had not selected a "Main QML file" in the Run Settings. The default is "<Current File>", whatever that means, and causes the “No qmlviewer or qmlobserver found” message. If I select a "Main QML file", I can run it as expected.

This behaviour applies to Qt Creator 2.3.1 as well, and any Qt versions I have tried. Does anyone know what "<Current File>" is supposed to be used for, and how? The “No qmlviewer or qmlobserver found” message I would assume is simply a bug, or am I interpreting it the wrong way?

Here the link
"QTCREATORBUG-6604":https://bugreports.qt.nokia.com/browse/QTCREATORBUG-6604

Did you spot "this":http://developer.qt.nokia.com/forums/viewthread/754 topic?

Perfect! Thanks!

Well, after some test, I found it was because I did not add this:
DEPENDPATH += ../
it seems that having only INCLUDEPATH += ../ is not enough.

Thanks!

it seems to boil down to installing the qt plugin in eclipse?

bq. If you use google search, you would find, e.g.
Adding New Custom Wizards [doc.qt.nokia.com]
Extending Qt Creator Manual [doc.qt.nokia.com]
File templates in Qt Creator [qtcentre.org]
just to mention the first three hits :-)

Thanks a lot!
That was helpfull.

added log.

[quote author="uelkfr" date="1321815789"]I have just installed Qt Creator, really great tool. An idea came to me that I would suggest to Qt Creator's developer team. ... [/quote]

A good place for such suggestions would be http://bugreports.qt.nokia.com.

"QTBUG-14056":https://bugreports.qt.nokia.com//browse/QTBUG-14056 has a workaround. It's a known problem, but without a good solution, tough.

Yes, it uses Python 2.7.2.
@[kermit@kermit ~]$ gdb
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) python print "Test"
Test
(gdb) @

"Debugger log":https://gist.github.com/1373481

Kermit.

Well, I think it will be as big as Qt SDK, but, the main problem I have is, how to setup that (by QMAKE)...I am quite Llama to do that (I understand to that, but I don't have )...I was also looking on Qt Creator QMake, but it didn't help me at all (yes, I was inspired by some useful functions)...

Not good, it turns off too much.

When I create a new opening curly bracket, and hit "return", I do want the closing bracket to appear automatically.

I just don't want any such thing with double quotes.

OK I have built the Qt SDK using the win32-msvc2010 and now have an x64 build of Creator. However when I launch this I get a Windows console appearing telling me it "Cannot update Qt version information: c:/qtdsk/desktop/qt/4.7.4/msvc2008/bin/qmake.exe cannot be run."

Now this kind of surprising as I don't even have a c:/qtsdk on my hard disk! And as a consequence of this it cannot autodetect my Qt Version (which I have set using QTDIR along with a QMAKESPEC) in my environment.

Is there anyway I can 'fix' this at all? I built Creator using QCtreator from the stand alone Creator source and .pro file using a heirarchy of :
@
C:\Qt
l----4.7.4
l----qtcreator-2.3.1
l----qt-creator-2.3.1-src
@

P.S. I know this build isn't compatible with the Intel Compiler.

Read the "qmake manual":http://developer.qt.nokia.com/doc/qt-4.7/qmake-project-files.html, espcially section "Declaring Other Libraries".

You're welcome. Feel free to edit the topic to "[Solved] ..." if it has been solved for you to indicate that it actually is and that there is a solution inside.

You went into debug mode and straight out of it again:-) Debugging is done once the application finishes.

Try setting a breakpoint somewhere.

Well I've simplified it...Now it works (not as I planned, but better than nothing)...

from git tag v2.3.1
fixed this issue. libExtensionSystem was not found by ldd.