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

[Adam Treat]

If my memory serves me the problem was that Apple couldn't figure out how to get cmake installed on the Apple build system machine.
________________________________________
From: webkit-dev-bounces at lists.webkit.org [webkit-dev-bounces at lists.webkit.org] on behalf of Dirk Pranke [dpranke at chromium.org]
Sent: Thursday, April 12, 2012 2:06 PM
To: Patrick Gansterer
Cc: WebKit Development
Subject: Re: [webkit-dev] CMake for Apple's Windows port

I think this is great; I've been meaning to spend some time on the
apple win port trying to fix the remaining bugs holding up the switch
to NRWT, but the fact that the apple win port still uses VS2005 is
definitely an impediment (yes, I can probably just pull the binaries
down from a bot for my purposes, but I'd really like to be able to
build it).

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?

Can someone from Apple weigh in on whether switch to CMake would be feasible?

-- Dirk

On Thu, Apr 12, 2012 at 5:41 AM, Patrick Gansterer <paroga at paroga.com> wrote:
> Hi,
>
> it's more than a year since the last discussion about the build system of Apple's Windows port. In the meantime I merged most of the general changes into the CMake files in the repository and have a working patch with a few CMake files at [1] as written in [2]. I don't think that it is ready to replace the existing vcproj files already, but I like to hear all points needed to do that.
> Adding CMake files for the WinCairo port (which uses the vcproj files too) will be very easy when the Apple version has been added.
>
> Here some benefits to the CMake version:
> 1) Shared build system: The shared files are already used by the Blackberry, EFL and WinCE port, so only the list of platform specific files needs to be maintained.
> 2) No dependency on cygwin [3]: The CMake build system searches for the Win32 version of the required executables (bison, gperf, flex, perl and python) like the WinCE port does already (see [4]).
> 3) Less Solution targets: Some of he current vcproj files only used for triggering Makefiles. The vcproj generates more native vcproj files, which e.g. allows clicking on one of the IDL files to generate the corresponding files.
> 4) Easy creation of Visual Studio 2010 project files [5]: Using CMake allows an easy transition to other (newer) Visual Studio versions, since every developer can choose his preferred version.
> 5) It's possibe to create Makefiles: The output of the windows buildbots shows much unwanted messages. Using Makefiles on the bots can produce cleaner logs and take advantage of all cores when used with JOM [7].
>
> Would be great if people who use the current VS Solution can give the CMake version a try and provide some feedback about it.
>
> BTW: There is also a patch to switch Wx to CMake at [8], but it did not get a positive response.
>
> [1] https://bugs.webkit.org/show_bug.cgi?id=72816
> [2] https://lists.webkit.org/pipermail/webkit-dev/2011-February/015831.html
> [3] https://bugs.webkit.org/show_bug.cgi?id=48166
> [4] http://trac.webkit.org/wiki/WinCE#Build
> [5] https://bugs.webkit.org/show_bug.cgi?id=53445
> [6] https://lists.webkit.org/pipermail/webkit-dev/2011-January/015815.html
> [7] http://qt-project.org/wiki/jom
> [8] https://bugs.webkit.org/show_bug.cgi?id=73100
>
> -- Patrick
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________
webkit-dev mailing list
webkit-dev at lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.