[Webkit-unassigned] [Bug 36529] [Qt] Compilation error on Qt for Embedded Linux built with -qconfig medium

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=36529





--- Comment #11 from Tasuku Suzuki <tasuku.suzuki at nokia.com>  2010-03-28 17:56:18 PST ---
(In reply to comment #10)
> (In reply to comment #9)
> > (In reply to comment #7)
> > > (From update of attachment 51494 [details] [details] [details])
> > > The patch itself is fine, but I don't think we should add these defines, as
> > > WebKit cannot be used without codecs. Therefore the right thing to do is to
> > > disable the compilation of WebKit altogether if Qt is compiled with
> > > QT_NO_TEXTCODEC.
> > 
> > (In reply to comment #8)
> > > (In reply to comment #6)
> > > I'm wondering about this one, too. The API is rendered almost useless if it's
> > > not possible to access the actions. There isn't much you can do with WebKit if
> > > you don't have QAction objects.
> > > 
> > > Tasuku, what's the use-case for this? Shouldn't WebKit be disabled in this
> > > configuration instead?
> > 
> > From a general browser point of view, WebKit is useless without these two
> > features. On the other hand, for people who uses WebKit as a platform for html
> > and javascript apps, it can be useful even if such features are not available.
> > WebKit should be enabled as much as possible.
> 
> Even if you just want to display html and run JavaScript you're going to need
> text codecs, to properly convert the 8-bit input into unicode.

I see. I'll find a way to disable WebKit when Qt is compiled without textcodec
support. How about QAction?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.