Hi Michael, On Fri, Jan 9, 2015 at 11:07 PM, Michael Jackson <[email protected]> wrote:
> > On Jan 9, 2015, at 2:20 PM, Andreas Pakulat <[email protected]> wrote: > > Also, I think part of QtCreator's problems with CMake files is that >> QtCreator only considers the top level code blocks file that is generated. >> There are other code block files within the build tree that fully describe >> all the files for a project, include paths, compiler invocations and things >> like that. This is leading to other problems with include paths not being >> found (See bug reports). >> > > Really? My cmake 3.1 generated just 1 cbp file at the top, that contains > all kinds of information. Including several targets with include-dirs per > target and a long list of source files and headers. This is on Linux with > the CodeBlocks+Ninja generator. > > > This is from the top level of my build directory on OS X. I'll have to > check when I get back to my Linux machine. This is with CMake 3.1.0. > > 503:[mjackson@ferb:Build]$ find . -type f -name "*.cbp" > ./Applications/DREAM3D/DREAM3D.cbp > ./Applications/PluginMaker/PluginMaker.cbp > Ah, let me guess, each of these directories has a CMakeLists.txt in the source tree with a project() command in it? I don't have a project that complicated luckily :) There's only a single project command in the whole cmake tree. Andreas
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
