Some building questions

[Morea]

Hi.
I've managed to build Qt programs by giving the commands
qmake -project
qmake
make -f Makefile.Release

But I'd rather just do

qmake -project
qmake
make
and get the executable in the current directory. Not in the Release directory. How can I do that?

The second question is: Are the programs dynamic or static built? Can I swtich between these two modes in any easy way?

[Cesar]

I hope refering to QtForum won't be punished
Here's a solution for your first question.

[Morea]

Nice! Now I need some help with a custom made makefile.

all:
     qmake -project
     qmake
     make

all:
     qmake -project
     qmake
     make

To copy to clipboard, switch view to plain text mode 

The line

CONFIG -= debug_and_release debug_and_release_target

CONFIG -= debug_and_release debug_and_release_target

To copy to clipboard, switch view to plain text mode 

should be added to the <projectname>.pro file automatically, how can I do that in a nice simple automatic way?
Any ideas?

[Cesar]

You might do one of the following:

• qmake -project "CONFIG -= debug_and_release debug_and_release_target"
• qmake "CONFIG -= debug_and_release debug_and_release_target"
• Comment out debug_and_release and debug_and_release_target from %QTDIR\mkspecs\win32-g++\qmake.conf file

[Morea]

So simple! Thanks, now I finaly almost have a working Dev-C++ and Qt environment!

[jacek]

Nice! Now I need some help with a custom made makefile.

all:
     qmake -project
     qmake
     make

all:
     qmake -project
     qmake
     make

To copy to clipboard, switch view to plain text mode 

You might run into troubles with such rule. "qmake -project" will include in your .pro file all files that look like sources from the current directory and all of its subdirectories. If there will be some autogenerated files left (for example moc output), you might get linker errors.

[Morea]

Yes, but if I use a separate directory for each project I will stay clear of the problems.
Yes, it's a mess, but dev-c++ is a total crap when it comes to Qt integration.
I'm waiting for a Qt and C++ development IDE.

But regarding the moc files, I've tried to rebuild the code a few times and it seems to ignore the
moc_mainwindow.cpp file.
Is this qmake beeing clever and making a good guess about files beginning with moc_ ?

[jacek]

Is this qmake beeing clever and making a good guess about files beginning with moc_ ?

I guess it's clever enough to skip them, but I recall that few people had problems with too much entries in a .pro file.