webkit-list at ericbrunstad.com
Mon Jun 22 16:19:14 PDT 2009
Is it possible to replace a DLL used by the compiled WebKit with a
newer version of the same DLL without recompiling WebKit? I need to
link my application with CFLite but your compiled version of WebKit in
CallJS does not include a CFLite library file (only a DLL). Your
requirements package has a DLL and a library file though. Can I just
delete the DLL without a library file and copy in the one from CallJS
or will that not work? If not, would you be willing to build me a
copy of WebKit with the CFLite library file intact? I would be
willing to pay if necessary. I have tried extensively to build the
source, but I always get errors that I think are related to using
Visual Studio 2005 Express. Would buying Visual Studio 2005 Pro make
building WebKit work more seamlessly? I'm not sure I would have much
use for it other than building WebKit, so I would rather not buy it if
I don't have to.
On Jun 21, 2009, at 11:38 PM, Brent Fulgham wrote:
> Hi Eric,
> On Jun 21, 2009, at 7:30 PM, Eric Brunstad <webkit-list at ericbrunstad.com
> > wrote:
>> I have developed a Mac application that I am porting to Windows.
> You can try my port of the Apple example program "CallJS"; it's an
> attempt to illustrate a Windows program using WebKit, interacting
>> right in to applications and freely distributed?
> Not really. I try to keep a build on my iDisk (same spot as that
> example), but it's a bit out of date.
> To be freely distributed, you can't use the CoreGraphics,
> CoreFoundation, or CFNetwork dll's. I've managed to ressurect
> Apple's original Windows Cairo port (you can see some further info
> on http://lest.blogspot.com.) It's currently built using CFLite ( http://sourceforge.net/projects/opencflite/
> , Apple's Open Source portions of the full CoreFoundation), cURL for
> the network stack, and Cairo for graphics.
> For a full example of what it's capable of, check out the
> Appcelerator Titanium project's Windows port, which uses this build
> of WebKit.
> Pretty much all of the Cairo logic is in the tree, with the
> exception of a small patch to conditionalize printing in
> WebFrame.cpp. I've tried to provide dll's for the build
> requirements on my iDisk, and have had a few independant reports of
> successful builds.
> Let me know if I can provide any further info.
More information about the webkit-dev