On Fri, Apr 16, 2010 at 9:57 PM, Nico Weber <[email protected]> wrote: > This is from an earlier thread on this issue on webkit-dev: > > """ > We also considered CMake, and had it demonstrably working for some of > our smaller projects as well. Unfortunately, transitioning to CMake > would have required moving everything over at once, without allowing > for some existing projects to be maintained "by hand" during a > transition period. CMake-generated files contain absolute paths, so a > .tar or .zip of the source tree could not be primed with CMake output, > complicating the "bootstrapping" process for new contributors. A less > significant factor was that CMake introduced an additional binary > build prerequisite, which would have had to have been installed > everywhere. Python is already a prerequisite for Chromium, so a > Python tool was easier to deploy.
I think you could do it part way. CMake has a new feature called external_project that allows you to download/configure/build packages using any build system. -Bill _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
