[webkit-dev] CMake for Apple's Windows port

[Mark Rowe]

On 2012-04-18, at 18:43, Patrick Gansterer <paroga at paroga.com> wrote:

> 
> 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 <dpranke at 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.

We don't have anything of this nature available for external consumption at this time.

> 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.

That's the direction we're heading in for the Mac build system. If this can be made to work with CMake then that's wonderful.

> 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. ;-)

I'll let someone else speak to these points.

- Mark


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120418/78215f0c/attachment.html>