Re: [Pyobjc-dev] WebCore support
Brought to you by:
ronaldoussoren
From: Ronald O. <ous...@ci...> - 2003-06-28 21:09:09
|
On Saturday, Jun 28, 2003, at 22:58 Europe/Amsterdam, Ronald Oussoren wrote: > > On Saturday, Jun 28, 2003, at 22:41 Europe/Amsterdam, Jack Jansen > wrote: > >> >> On zaterdag, jun 28, 2003, at 15:01 Europe/Amsterdam, Ronald Oussoren >> wrote: >> >>> I've just checked in a patch that (amongst others) enables support >>> for the constants in the WebCore framework. To compile the current >>> CVS version you have to install the WebCore SDK. >>> >>> I have not yet check if the compiled version will work on a system >>> without Safari 1.0. I don't want to rely on optional applications, >>> so if the binary version does not work without Safari 1.0 I'll roll >>> back this part of the patch until we find a better solution. >> >> Purely by chance I have a machine that's still at Safari beta 2, and >> unfortunately PyObjC doesn't compile. I get a long string of error >> messages, starting with >> >> In file included from Modules/Foundation/_Foundation.m:233: >> Modules/Foundation/_Fnd_Enum.inc:103: >> `NSHTTPCookieAcceptPolicyAlways' undeclared here (not in a function) >> >> So I think we should leave this out. > I already suspected that this would be an issue. What is IMHO more > important is: does a PyObjC compiled on a system with WebKit work on > that system. I'll be testing that later on a machine at work. It doesn't. The only additions to Foundations are some constant definitions, including some NSStrings. I think those cause these problems. Maybe weak-linking will work for that. Ronald |