[haiku-development] Re: Should ICU headers be installed?
- From: Ryan Leavengood <leavengood@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 26 Jan 2010 13:08:05 -0500
On Tue, Jan 26, 2010 at 10:22 AM, Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
>
> But ICU is currently considered private, i.e. it is not part of haiku's public
> API (that's why there are no headers provided for it). Admittedly, it's hard
> to tell, since all the libicu*.so-libs live in /system/lib, while they should
> probably be moved into something like /system/lib/private.
That might be a good idea.
Also I don't think it would be terribly difficult to remove the
dependency on ICU in our WebKit port and just rely on the Locale Kit.
Of course this assumes the Locale Kit exposes whatever ICU
functionality that WebKit uses (which I don't think is all that much.)
But given the current state of the Haiku WebKit port, there are more
important issues to tackle before this one. But the main point is that
this dependency on ICU is not necessarily permanent (in WebKit, I
can't say for other ported libraries or software.)
> Right, that's why I think all those libraries should be moved out of haiku
> into separate packages. That's more or less the only way to avoid the
> situation of mismatches between system-provided and application-provided
> libraries.
Indeed. Though again in this case we could at least remove the WebKit
dependency on the image libraries by using the Translation Kit
(assuming it doesn't introduce an unacceptable performance penalty.)
Finally a general note to Stephan: please get in contact with me or
Maxime in regards to what work you are doing on WebKit. While I have
been idle on that project for some time, if I pick it up again soon I
don't want to work on the same things as you. From my side I still
have a fix for mouse hovering to commit and push upstream so if you
notice that bug don't worry about it :)
--
Regards,
Ryan
Other related posts:
