[Qt5-feedback] Build system requirements for Qt5
Doug Schaefer
cdtdoug at gmail.com
Wed Jun 8 21:33:32 CEST 2011
On Wed, Jun 8, 2011 at 2:41 PM, Alexander Neundorf <neundorf at kde.org> wrote:
> On Tuesday 07 June 2011, Thiago Macieira wrote:
>> On Tuesday, 7 de June de 2011 08:16:03 Bill Hoffman wrote:
>> > Agreed, it was a bit insane. It would be really helpful if you could
>> > post some pseudo code that showed the use case of win32 sources and some
>> > sources that depend on some system introspection value. What does that
>> > input look like, and how does it work?
>>
>> I don't know. What I'm asking is: you guys who have more experience with
>> build systems, can you figure out something that is both IDE-friendly and
>> human- friendly?
>>
>> The IDE needs to be able to get the file listing from any project, it needs
>> to build any project, it needs to get the compiler options (especially the
>> preprocessor options, -I and -D) for every single file file,
>
> All this is trivial to do with cmake.
>
> E.g. for the Eclipse CDT generator, it generates rules to build every single C
> file, to preprocess it only, to compile it to assembler, and it also puts the
> information about include dirs and definitions in the project file, so Eclipse
> can do correct highlighting.
Are there ways to get the include dirs and defs in other generators,
for example if we're using the makefile generators? I'd prefer to have
CDT call CMake and make, similar to what Qt Creator would do, but
still have access to this information somehow.
More information about the Qt5-feedback
mailing list