Qt Creator and other tools

The UTF-8 BOM was present in my pro files and qmake doesn't seem to like it.

I removed them with option in QtCreator.
All is fine now

Be sure and mark the thread as [Solved]. Thanks!

I'm using fully updated Qt SDK on windows so it's Qt 4.7.4 atm. I just wanted to try Clang, so I can wait for a stable Qt 4.8 and working version of Clang for windows. There's no rush :). Thanks for answer.

My path includes a mysql driver. Peppe wins :(

Oops, i forgot to add the solution to my original problem in this thread. Its as follows:
if getting errors: undefined reference to `snd_pcm_open etc
Solution:
Add the following line to the .pro file:
@LIBS += -lasound@

The debugger stops at the first breakpoint found. If it stops earlier, there is either another breakpoint or an application error which forces the debugger to halt the application.

In addition, you cannot "jump" to a specific breakpoint. Your application will have to follow the program flow until it reaches to code triggering the breakpoint.

i did uninstalled it and reinstalled it in another drive and it work fine now :D...thank u :D

Why don't you just use shadow building?

Just do create a directory "linux" next to the directory holding your sources, change into it and do qmake ../sources/myprofile.pro and you have all your linux stuff nicely separated from the sources. Of course you can have several other build directories in parallel, each with their own settings.

Removing all assert statements in the code solved the problem, sorry for the very long delay in updating the thread.

I solved my problem, in probably an ugly way. I discovered that Qt Creator offers extra build steps, that you can place before or after the supplied build steps. In case it helps somebody else, here's the entry I made. Click the Project tab.

Enable custom process step. (checked)
Command: "c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\nmake" -f m4.mak
Working directory: C:\Users\Rick\bazaar_repository\data_struct
Command arguments: (empty)

Rick

Sorry, I am no expert in that area:-( I think you will find better answers to such Symbian specific questions on developer.nokia.com (note the missing Qt in the URL).

Are the relevant C++ header files set up correctly for your project (e.g. by using QT += network or whichever module you are using)? That is needed for both building the stuff as well as using it, so if your project does run fine then the code completion should also work.

sorry, my english is very little.

what is compiler for Opengles 2.0 vertex and fragment shader on N9, N950?

The trick is this:

In your form, place two QWidgets, one for each of the pannels. Put those two widgets in a horizontal layout. now, set the size policies of the widgets, so that the left one is fixed, and the right one is minimumExpanding. Next, put the contents of your form sides inside these widgets, and again apply a layout to each of the created "panels". Note that you can also use some other widget (like QFrame or QGroupbox) instead of QWidget if that suits your needs better.

A common solution is to build the application using the libraries and headers files found within the source directory. If you want that your application can be built using both (system-wide and local) just add a conditional to your .pro file.
@
// toplevel.pro

SUBDIRS += lib app
CONFIG += ordered // make sure lib is built before app

// app.pro

exists(/usr/include/yourproject.h) { // system-wide includes installed
INCLUDEPATH += /usr/include
LIBS += -L/usr/lib
}
else {
INCLUDEPATH += ../include
LIBS += -L../lib
}
@
Brain to terminal. Not tested.

make install then copies the includes and libraries to their system-wide places, so that other applications can use it as well.

A more sophisticated solution would be using "qmake features":http://doc.qt.nokia.com/latest/qmake-advanced-usage.html#adding-new-configuration-features as for example "QCA":http://delta.affinix.com/qca/ does.

I do think we mention the need to have the debugging tools installed in the installation as well as the documentation.

If you think about it, there is no way for Qt Creator to add anything useful for you in that situation. What you normally put there are a number of variable names or constants, but Qt Creator cannot possibly know which ones.

Or just ask for a status update in the bug report directly.

You should mark your post with [Solved] in the subject line.