I cannot configure my projects or build my projects in Qt Creator 2.5.8 but I can in 2.4.1

[vincegata]

Hello,

I want to use Qt Creator 2.5.8 because it can work with gnome-terminal however when I opened my projects in 2.5.8 I cannot build them, when I go to ->Projects I get a message:

"Qt Creator can use the following kits for project FixEngine:
No valid kits found

The project FixEngine is not yet configured.
Qt Creator uses the kit Desktop to parse the project.
Please add the kit in the Options or via the maintenance tool in SDK."

When I do Import Build From it says FixEngine.pro is not found but it is there, this is how 2.4.1 works.

Any ideas how to fix this?

Thank you.

Edit: I am on Ubuntu, I am using my own makefiles and non of the Qt stuff. I just want Qt Creator to pick up my makefiles to build the projects.

[sierdzio]

There is no Qt Creator 2.5.8. The newest stable is 2.5.2. If you are using the unstable 2.6, the version reported would be 2.5.81, or 2.6.81 for master branch.

I don't quite know what kits are you talking about, but since you are using your own makefiles, you can probably just ignore the "project is not configured" message, and proceed to Edit tab on the left pane.

And if you really want to configure, you need to set it up by hand - choose how to use qmake, if you are using it, and specify make commands.

[tobias.hunger]

Please go to Tools->Options->Build & Run->Kits and set up one kit to use. At least fill in the device type, device (most likely desktop) as well as the tool chain and debugger. For qmake-based projects you will also need a qt version and mkspec (which can be empty if you are ok with the default one).

You might need to define Qt versions and tool chains first (other tabs on the same options page).

Creator needs this information to know how to parse your compile output and debug the results.

[vincegata]

[quote author="Tobias Hunger" date="1346932532"]Please go to Tools->Options->Build & Run->Kits and set up one kit to use. At least fill in the device type, device (most likely desktop) as well as the tool chain and debugger. For qmake-based projects you will also need a qt version and mkspec (which can be empty if you are ok with the default one).

You might need to define Qt versions and tool chains first (other tabs on the same options page).

Creator needs this information to know how to parse your compile output and debug the results.[/quote]

It worked - thank you.

To set up a kit I had to specify a path to qmake, which I do not use. I wish there was an easier way to set up projects for us who do not use any of "Qt", on the other hand I do not do it very often.

[tobias.hunger]

vincegata: With kits you don't need to give a Qt version, provided you do not use qmake to build your project.

[vincegata]

I had to, o.w. it took me to configure kit every time I clicked on Projects.

[tobias.hunger]

As I said: "With kits you don’t need to give a Qt version, provided you do not use qmake to build your project."

You are using qmake to build your project.

[vincegata]

I certainly do not use qmake to build my projects, I never did, I use my own makefiles with Linux's make.

[vincegata]

[quote]As I said: “With kits you don’t need to give a Qt version, provided you do not use qmake to build your project.”
You are using qmake to build your project.[/quote]

I went to Projects and clicked on Manage Kits, set Qt version to None, clicked on Edit and then I clicked back on Projects now it says "No build options available".

I went back to Manage Kits, set Qt version to 4.7.4 (is the only available in dropdown) now I can configure my build settings. When I configure build settings I remove everything that's set by default and add Custom Build Process and type for Command: make; for Arguments: FixEngine. FixEngine is my project for which I set up my makefile.

Hence, I use qmake or not, it does forces me to set Qt version.

[tobias.hunger]

Your post mentioned FixEngine.pro, which does look like a qmake file. qmake generates Makefiles from that which are then used by make to actually build the whole thing.

[vincegata]

I see now, I thought *.pro files are the project files that are Qt-agnostic.

[bagustris]

I have the same problem, the solution didn't solve my problem.
Here is I got when set up kit in tools --> option -->Build & Run:

qt version --> none

I got this problem after upgrading from qt4 to qt5.
Anyone knows how to add qt version in this kit setup>

[tobias.hunger]

bagustris: Please do not abduct other people's posts with your own. Open a new thread instead.

Having said so: If there are no Qt versions defined, add some:)