[Qt5-feedback] Qt5's qmake
Kishore
kitts.mailinglists at gmail.com
Thu May 12 20:20:16 CEST 2011
On Thursday 12 May 2011 11:04:53 PM Konstantin Tokarev wrote:
> 12.05.2011, 21:27, "BRM" <bm_witness at yahoo.com>:
> > might I add that it needs to be able to function recursively very well.
> >
> > Presently I have a number of projects where to keep things simple, I use
> > sub-folders to manage portions of the code. For example, in a protocol
> > library I push chunks of the protocol (e.g. calibration) into its own
> > folder. However, presently I have to be very careful about the naming of
> > all the files throughout the entire project as no two of them can be the
> > same; otherwise QMake will build both, but only one object file will be
> > kept for linking. This is a rather simple thing that QMake should be
> > able to handle internally.
> >
> > Note: We didn't want "yet another tool", so CMake didn't make it into the
> > picture. Otherwise we might be on CMake as opposed to QMake. I generally
> > like QMake; but there are a few major short-comings, like the above,
> > that could really improve the ability to work with it.
>
> I also like QMake in general; but syntax of custom function definition is
> unintuitive - it's difficult to remember where $$ should be used and where
> should not; it also lacks traditional definition of function arguments. I
> also miss CMake-like macros.
I find qmake most useful when creating single main.cpp projects for some simple
code testing/experiments.
qmake --project
For anything more involved, i tend to use cmake. It is the easiest way i know
to create boiler plate Qt makefiles for throw away test projects.
--
Cheers!
Kishore
More information about the Qt5-feedback
mailing list