Re: [webkit-dev] Minimum supported Xcode version is changing
On Sep 20, 2013, at 18:25 , Mark Rowe mr...@apple.com wrote: On 2013-09-20, at 1:01 PM, Mark Rowe mr...@apple.com wrote: On 2013-09-20, at 12:59 PM, Bem Jones-Bey bjone...@adobe.com wrote: Did you fix it so that the build works on Mountain Lion when running Xcode 5? As of yesterday, the tree didn't build on Mountain Lion with Xcode 5, with the following linker error: Undefined symbols for architecture x86_64: __kCFURLCachePartitionKey, referenced from: _WKCachePartitionKey in libWebKitSystemInterfaceMountainLion.a(WebKitSystemInterface.o) __CFHostIsDomainTopLevel, referenced from: _WKIsPublicSuffix in libWebKitSystemInterfaceMountainLion.a(WebKitSystemInterface.o) I’ve never been able to reproduce this error myself. The WebKit nightly builds have been built with Xcode 5 for the last week or two now without problems. If you can email me your entire output of build-webkit off-list I’ll see if I can spot what’s going awry. This should be fixed with r156218. It works for me now, thanks. - Bem ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Announcing new port: Nix
On 13 sep 2013, at 01:58 em, Hugo Lima hugo.l...@openbossa.org wrote: On Fri, Sep 13, 2013 at 4:31 PM, Antonio Gomes toniki...@webkit.org wrote: So will you advocate your users to use your external GitHub version or the one in WebKit? Please consider not being half upstream. It wont be half upstream, but the github repository will be for example a fallback for a working bleeding edge Nix just in case of WebCore changes that break Nix on webkit.org. We can also push things first there then on webkit.org if a faster development pace if needed, as all Nix developers use git this also means that experimental feature branches will exists on github repo too (don't tell me about create svn branches). Please correct me if I’m misunderstanding this, but: - You are OK with WebCore changes breaking the Nix port - You are going to have a “stable fork” of Nix in another repository (GitHub). If this is the case, what benefit does having the code upstream provide to the WebKit project as opposed to having it live out of tree and upstream changes that are of high value to the WebKit project itself. Note that I’m not against the Nix port, but maybe this would be a good way for a port to “prove that it’s worthy of being upstreamed. I don’t remember when the last port was added to WebKit, but I’m pretty sure it was many years ago and the project has changed significantly since then. (I’m also a bit confused about why the Nix “Platform” layer needs to live in the WebKit repository - we don’t have Windows or AppKit headers in the repository and I don’t understand why Nix is different). Thanks, - Anders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
