[Solved]Qt generic project

stukdev

Where you read this?
Can you explain in details the problem?

Peppy

I read it in Qt SDK Documentation at "Home" page is below link to "Generic Project" or something like that...

tobias.hunger

Just "check the documentation":http://doc.qt.nokia.com/qtcreator-snapshot/creator-project-generic.html.

Peppy

Yes, that I've read earlier. But It's able to connect with Qt SDK/API ?? In order to make my own project tree structure as I wish to do and apply Qt framework ?

So my meaning (of this generic project) is: Create your own project structure with your source files and add some makefiles which you write yourself and set up it as wish you want, add to QtCreator main make and build it installed compillers...

(as I requested "here":http://developer.qt.nokia.com/forums/viewthread/4147/)

Is my meaning of generic project correct or not??

[EDIT: fixed link, Volker]

tobias.hunger

It is a Makefile based project... you can do whatever you can do with the buildsystem of your choice.

Peppy

That's nice...I'll try it in near future...I hope it will be much more funny :)...I am excited...

Chuck Gao

You can also read "Advanced qmake usage" for the project definition

tobias.hunger

Chuck.Gao: You are waaay off with your comment: The generic project does not even use qmake (well, in theory it could generate the Makefiles run by the "generic project" using qmake, but that would make no sense at all).

Chuck Gao

[quote author="Tobias Hunger" date="1305644453"]Chuck.Gao: You are waaay off with your comment: The generic project does not even use qmake (well, in theory it could generate the Makefiles run by the "generic project" using qmake, but that would make no sense at all).[/quote]

Thanks Tobias, i miss understanding the topic. And i find the detailed information in Assistant.

Peppy

QMAKE is for me deprecated. It has no way how to change makefile output dir, and for this reason, it is out of my task...

The latest SDK which I downloaded, has come with jom.exe file (I would like to know more about this executable)...

tobias.hunger

Peppy: Why would you care where the output of the build system is written to? That is a implementation detail of the build system. Use shadow building if you do not want to have temporary build files litter your source directory.

Or are you talking about where the stuff gets installed to? That can be set with qmake.

Peppy

That just my meaning, that sources shouldn't be mixed with makefiles, but it is my opinion... I have a bad habit from Visual C++, where everything has own place, you know...

I will have to change my project tree structure and spend more time with project planning...

tobias.hunger

Peppy: That is what shadow building is for. You create a empty directory next to the one holding the sources and everything qmake or make creates goes there.

goetz

I not know anybody with a project of reasonable size who uses homebrewn Makefiles these days. They are a nightmare to maintain and are in no way cross platform.

Peppy

School projects at college requires (the same or simillar) structure as I mentioned in another topic (linked above)...

tobias.hunger

Oh, school... it is no reasonable sized project then:-)

goetz

And hardly any sensible project requirements :-)

Peppy

Yes, it's silly, but what can I do?! Just do it as they want...

goetz

qmake has the -o switch to specify where the output should go. Maybe this can work for you.