Hi Ariya, Thanks for your help. I've gone through what you've written in the link provided below. It's good. However, I want to tell you that when I write here, it means I've done enough of R&D over Google and various WebKit related links before that. None of the topics questioned or answered therein, suits what I'm looking for over here.
Is it absolutely necessary that if I need to build WebKit for ARM, I need to do it with one of its ports? In that case, which would be the suitable port providing only the parsing/rendering part? -Pritam. On Thu, Dec 17, 2009 at 12:19 PM, Ariya Hidayat <[email protected]>wrote: > You also might want to read first what I've written here: > > http://lists.macosforge.org/pipermail/webkit-help/2009-August/000146.html > > > Like Holger wrote in his answer, modifying (and refactoring) one of > the ports to suit your need is likely a better solution than creating > a new port from scratch. > > > > > -- > Ariya Hidayat > http://www.linkedin.com/in/ariyahidayat >
_______________________________________________ webkit-help mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-help
