Qt Creator and other tools

Oh, thanks. I've always run designer as a separate program, so if it was in the Qt Creator SDK I never noticed it. I just brought up Creator, started a new project, clicked on mainwindow.ui, and it went to Design. It seems to be working fine. Thanks.

I may be calling them the wrong thing, but the "win32:" and "unix:" tokens at the start of lines like this:

@win32:INCLUDEPATH += "C:/mylibs/extra headers"
unix:INCLUDEPATH += "/home/user/extra headers"@

any ???

I was asking an "or" question as to which is better but if I use Dropbox I guess I can provide both. Great idea!

Thanks!

-Bryan

Both set. These are in my Windows system path. Opening the project file in Visual Studio works just fine, compiles and links with no errors. It's just within QtCreator that I encounter these linker errors.

I have encountered some debug problems,
if you compiled the QT source with mingw 4.4 and try to debug with pythondb(shipped with old QT SDK), maybe the debug helper used old python version( 2.5),
"here":http://115.com/file/e7lbuza2# is the new version debug helper, pythondb(python 2.7),I extracted from QTSDK 1.3.

The website is in Chinese, if you have any problem to download it, send me a message.

Well, bat spit.

It appears that in my late-night haste to get multiple things working, I somehow failed the MinGW check-box.

All is better now...thanks, Andre. I guess I shouldn't work so late.

Qt Creator itself is built against Qt 4.7.4. It brings its own set of Qt libraries with it and does neither rely on nor ever use your system installed Qt. So this behavior is perfectly ok.

Its always pain to add/remove/manage libs on windows.

Did you think about managing dependencies to external third party libraries?

What I'm thinking about is a central lib repository like maven and an equivalent dependency management. That is easy!

ok, outside of my experience. But thanks for sharing, I have learnt a bit more :-)

Yes, sure. I agree.

Nevertheless, it is not mandatory to change (or, even worse, destroy) the existing project.

A single class (or a file containing more than one class) could be easily copied into a new project (containing all of the required support code) and compiled as a library. I can easily do that by hand so I cannot see any reason why it cannot be done by (a reasonable complex piece of) software.

After all, when you "export" something from a project or a document, usually the original project/document remains untouched.

I could also imagine a GIT-based approach, based on branching. In this second case, the developer would get the added benefit of maintaining a explicit parent/child relationship between the original project and the exported component (and being able to merge back if required).

Posted a bug report.

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

-Thanks for filing the bug report. When you post the link to the bug report here, others are able to vote and monitor the progress as well.-

[Edit] Did not read careful enough and overlooked the link, which is already there :-(

[quote author="miroslav" date="1330425416"]I was referring to the fact that the wiki page did not mention that Valgrind can be used directly from within Qt Creator on the platforms that support it. [/quote]
Ah, right, good point, and thanks for the addition.

Well I use Qwt with Eclipse in Linux so that's not the problem.
This is how the qwt part of my .pro file look like:
@

INCLUDEPATH += /usr/include/qwt-qt4
LIBS += -lqwt-qt4
DEFINES += QWT_DLL
@

I just setup a Qt GUI project, build the qwt libs, add the above code to my .pro file and add the include paths in eclipse under project settings. It doesn't make sense that a 3rd-party tool would cause a Qt error like the one you got, maybe you accidentally replaced a Qt Lib path with a qwt one instead of adding it.

Ah, I see. Gotcha.

qmake.exe [PROJECT PATH] -r -spec win32-g++ "CONFIG+=release" // Windows Compile

Which IDE is using your co-worker?
It's so much easier to press 3 buttons to change a target, than typing in a command line ;)