Changes between Version 8 and Version 9 of WebKitNightlyElCapWorkaround
- Timestamp:
- Oct 20, 2015 11:48:33 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WebKitNightlyElCapWorkaround
v8 v9 1 With the introduction of OS X El Capitan and the // System Integrity Protection// security feature, WebKit nightlies no longer work. They still launch, but the latest WebKit frameworks included inside are ignored and the system version of WebKit is used. This is because our use of `DYLD_FRAMEWORK_PATH` is ignored when launching the system Safari (specifically the `SafariForWebKitDevelopment` binary in the Safari app bundle). We are preparing a fix for this in a Safari update, but until then you can apply the following workaround. (These steps will also help you run local builds of WebKit against Safari.)1 With the introduction of OS X El Capitan and the //[https://developer.apple.com/library/prerelease/mac/releasenotes/MacOSX/WhatsNewInOSX/Articles/MacOSX10_11.html#//apple_ref/doc/uid/TP40016227-DontLinkElementID_17 System Integrity Protection]// security feature, WebKit nightlies no longer work. They still launch, but the latest WebKit frameworks included inside are ignored and the system version of WebKit is used. This is because our use of `DYLD_FRAMEWORK_PATH` is ignored when launching the system Safari (specifically the `SafariForWebKitDevelopment` binary in the Safari app bundle). We are preparing a fix for this in a Safari update, but until then you can apply the following workaround. (These steps will also help you run local builds of WebKit against Safari.) 2 2 3 3 //'''Note:''' This workaround is not for the faint of heart, and requires you to run commands while booted into the system recovery partition. Proceed with caution.//
