On Apr 16, 2010, at 7:17 PM, Bill Hoffman wrote:
On Fri, Apr 16, 2010 at 10:10 PM, Marc-Antoine Ruel <mar...@chromium.org
> wrote:
Thanks Nico for digging up the archive.
As I said in the other thread, the people at the session mostly
looked about
reducing the number of build system, not forcing anyone to use any
tool. If
some teams wants to switch to CMake, prefect as long as the number
of build
tool reduces. Nobody seemed willing to switch to qtmake. Nobody at
the
meeting advocated for CMake.
I don't have first-hand experience about CMake but from I only
heard midly
negative comments. The generated xcodeproj and vcproj are far from
'native'
and from f2f discussion, at least one llvm guy isn't happy about
CMake and
would rather move it off. The 'native' IDE feel was very high in our
priority list, especially in XCode in fact.
It is as native as we can make it. However, we do call cmake during
the build at some points, to overcome shortfalls of the build tool.
Also, to re-run cmake if any of the input files change. Also, basic
system commands like cp can be done with cmake -E copy_file so it is
portable.
Calling cmake during the build would likely be a showstopper for the
Mac port. As far as I know, Apple's build farm does not have CMake
installed (at least not on older build trains). And it's not easy to
convince the build engineers to install custom build tools.
Regards,
Maciej
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
