On Fri, Apr 16, 2010 at 6:38 PM, Peter Kasting pkast...@google.com wrote:
On Fri, Apr 16, 2010 at 3:35 PM, Maciej Stachowiak m...@apple.com wrote:
I'm curious if the Chromium folks who created Gyp had any specific reason
that they ruled out CMake as an option. (I have heard that it was
On Fri, Apr 16, 2010 at 9:45 PM, Maciej Stachowiak m...@apple.com wrote:
FWIW, I don't have CMake installed, and I have everything a typical Apple
developer would have and then some. I'm running SnowLeopard and the latest
Xcode. CMake is also not installed by default on Windows and I am not
On Fri, Apr 16, 2010 at 9:57 PM, Nico Weber tha...@chromium.org 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
We can make binaries available through a convenient download script
(possibly one that gets a source drop and builds it) if we have to. In fact,
when WebKit first switched to Subversion, for a while you had to get your
own copy to even check out the tree.
Sounds good.
All I'm saying is
On Fri, Apr 16, 2010 at 10:04 PM, Adam Treat tr...@kde.org wrote:
On Friday 16 April 2010 09:58:17 pm Bill Hoffman wrote:
Also: how hard is the dependency on being installed? Is this a solvable
problem if it turns out to be a showstopper for some folks?
It has to be installed
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.
I am told they have it now
On 4/20/2010 5:13 AM, Maciej Stachowiak wrote:
1) None of the Mac builders have CMake installed.
2) The organization that maintains the Mac builders is not willing to
let teams use any build systems to build that do not come with the OS,
or to install any custom binaries on the builders,
7 matches
Mail list logo
