Hi Stephen,
On 18/01/2007, at 3:03 AM, Stephen Deken wrote:
On 1/17/07, David D. Kilzer <[EMAIL PROTECTED]> wrote:
There is nothing that says you can't ship your own copy of WebKit
(legal or otherwise)! OmniWeb does just that.
Strange -- I'd read some discussion (apparently from 2004) which
indicated the WebKit framework was not licensed for distribution:
http://lists.apple.com/archives/webkitsdk-dev/2004/Mar/msg00038.html
If this has changed since then, great! I love it when the solution
gets handed to me. :)
The email you reference was written prior to WebKit being open-
sourced. At that time you would have required Apple's consent to
redistribute the framework. Now that it is open-source, it is
permissible to do so. I'm aware of several applications that bundle
custom versions of WebKit -- OmniWeb and Sandvox being the most
recognized of that group.
Now my only problem is that XCode really, really wants to link against
the WebKit in /System/Library/Frameworks instead of my private copy.
Something is wonky with my linker settings, and I wasn't able to
discern exactly what it was in the few minutes I had this morning. I
wound up just setting DYLD_FRAMEWORK_PATH and
WEBKIT_UNSET_DYLD_FRAMEWORK_PATH to get it working, but obviously this
won't work when shipping.
How are you specifying which framework to link against? I believe
you'll need to either add the directory containing
{WebKit,WebCore,JavaScriptCore}.framework to Xcode's framework search
path, or change the framework references to use absolute pathnames.
If you're building using an SDK you may have slightly more issues, as
I encountered some difficulty in making Xcode cooperate when doing
this recently.
Cheers,
Mark Rowe
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo/webkit-dev
