I will say Thank You ... we use cmake as the base for nearly every new WebKit port we engage in.
We have a native Windows build that is cmake to replace the Apple/CF based one and it is so much easier to maintain than the previous collection of VS property pages and build configurations. Not only that but we can quickly generate multiple build variants (CF vs GDI for example) very quickly and also share project content in ways that make sense (such as with WinCE). We can count at least 6 ports we have done using cmake. We have rolled our own a couple of times on early ports, but on the last few with the 'in tree' initial base from WinCE and EFL we're now using that as a basis. So Patrick (and whomever else kicks in keeping the cmake builds running) ... THANK YOU. Thomas ------------------------------------------------------------- Crank Software Inc. Office: 613-595-1999 x511 Mobile: 613-878-4659 Online: www.cranksoftware.com <http://www.cranksoftware.com/> Check out: Crank Software¹s Blog <http://cranksoftware.com/blog/> There is a better way to build user interfaces for embedded devices. Download a 30 day evaluation <http://www.cranksoftware.com/products/eval.php> of Crank Storyboard Suite today From: Patrick Gansterer <par...@paroga.com> Date: Thu, 19 Apr 2012 03:43:28 +0200 To: Mark Rowe <mr...@apple.com> Cc: Dirk Pranke <dpra...@chromium.org>, WebKit Development <webkit-dev@lists.webkit.org> Subject: Re: [webkit-dev] CMake for Apple's Windows port Am 12.04.2012 um 20:06 schrieb Dirk Pranke: > Patrick, have you documented what all you need to install on a Win box > in order to be able to run CMake and do the build? You need to install CMake and the same tools listed at http://trac.webkit.org/wiki/WinCE#Build and http://www.webkit.org/building/tools.html (but without cygwin). Am 12.04.2012 um 23:47 schrieb Mark Rowe: > On 2012-04-12, at 14:28, Dirk Pranke <dpra...@chromium.org> wrote: >> Interesting. Can you comment further on why this is needed, instead of just >> checking out the whole repo? > > The short answer is that doing so would violate internal policies that we have > about what sorts of files are acceptable in the source of production builds > (for example, precompiled libraries are not acceptable). We also don't have > any desire to shuffle multiple gigabytes of layout tests around machines that > are only used for building. Is it possible to get a (detailed) list of requirements? It's hard for people don't knowing the internal Apple build process to work on it. Why isn't it possible to checkout only the Source directory? Since the current system has more than 1 VS solution too, I don't think it will be a problem to have more than one "root CMakeLists.txt" too. Is there a interest in getting rid of the Visual Studio files? Are there any points agains CMake we know already? I don't want to put (much) work into the CMake files for a simple "No, thanks" at the end. ;-) -- Patrick _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
