[Qt5-feedback] Build system requirements for Qt5

[Alexander Neundorf]

Hi Doug,

On Thursday 09 June 2011, Doug Schaefer wrote:
> On Thu, Jun 9, 2011 at 3:04 AM, Alexander Neundorf <neundorf at kde.org> wrote:
...
> > P.S. there is one major problem we (cmake) have with Eclipse+CDT: cmake
> > strongly recommends to use out-of-source builds, and it has the hard rule
> > that when generating the build files it must not write or change
> > anything in the source directory. So the .project and .cproject files
> > are created in the build dir. But Eclipse expects that the project file
> > is located at the root of the source tree, e.g. the svn support does not
> > work in linked folders. It would be nice if the project file could
> > simply have a tag <sourcedir> or <projectrootdir>, whose content, if
> > present, would be used instead the location of the project file.
> > Then, when opening such a project in Eclipse CDT, it would show the
> > contents of the source dir (instead of the build dir, as it is now), and
> > svn etc. would probably just work.
> 
> We should probably take this to another list. 

cmake-developers would be great:
http://www.cmake.org/mailman/listinfo/cmake-developers

> But I don't think CMake should be generating the .project and .cproject. 

Depends.
In general, my POV is not "let's build an Eclipse project using CMake", but "I 
have a project built with CMake, now let's generate input files for the IDE I 
personally want to use for working on it.".
This is the purpose of cmake, write one set of (cmake) scripts, and then 
generate input files for the IDE or buildtool of your choice, be it Xcode, 
VisualStudio, plain make, CodeBlocks or Eclipse.

> CDT should be calling
> CMake to generate makefiles as part of it's build process.

For the managed build project type, so you don't have to generate the 
makefiles yourself (i.e. CTD) ?
IMO this is possible too, but we'd like to know in more detail what you would 
need or how the workflow should look like.
(you could for instance include copy of cmake, and use this in the background 
to generate the makefiles, so you would basically already know everything)

cmake-developers is probably really better suited for this.

Alex