[Qt5-feedback] Build system requirements for Qt5
BRM
bm_witness at yahoo.com
Thu Jun 9 21:55:02 CEST 2011
----- Original Message ----
> From: Alexander Neundorf <neundorf at kde.org>
[snip]
> > - it needs to feed an IDE with a useful understanding of the project
> > structure (not some random foo.o targets whose existence the IDE must
> > divine out of thin air)
>
> CMake can easily put all existing targets into the project file for the IDE,
> the IDE doesn't have to guess them.
>
Last I used CMake, that really depended on what you wanted to do.
For instance, Header Files only made it into the output generated project (e.g.
VC++ project) _if_ you also wanted to do pre-compiled headers (which I
personally detest and don't use).
It was also very difficult to organize the files in the display of the IDE
output generated projects - e.g. grouping them together for logical purposes.
(There was a way to do it, I forget how off hand, but it wasn't very intuitive.)
So, I'd very strong advocate that whatever tool it has maintain QMake's ability
to differentiate between source and headers and put headers into the project
files, and even go one step further of being able to do IDE Display Folders so
that both could be logically organized - e.g. headers, headers\protocol, etc.
Again, It's been a couple years since I used CMake (2008?) so please correct me
if this has since changed. I certainly didn't see Kitware moving in that
direction at that time, so I doubt it has - but would be very happy if it did
change.
$0.02
Ben
More information about the Qt5-feedback
mailing list