[PATCH] Include <strings.h> on Solaris for bzero definition
Daniel Stone
daniel at fooishbar.org
Thu Apr 26 08:11:20 PDT 2012
Hi,
On 26 April 2012 16:46, Alan Coopersmith <alan.coopersmith at oracle.com> wrote:
> On 04/26/12 04:52 AM, Daniel Stone wrote:
>> I wouldn't be too hugely concerned about porting it to Solaris though
>> (unless you're porting Wayland too), since the amount of API we need
>> to expose to implement the XKB wire spec is totally unsustainable and
>> would mean we'd have very very little latitude to do anything with the
>> library, including working on a new file format. I think it'd make
>> more sense to just copy libxkbcommon into the server and go from
>> there.
>>
>> Which probably means the library needs a new name, I guess. Ho hum.
>
> Ah, I'd thought it was still considered as a potential replacement for
> xkbcomp in the server. Though now that we have working Intel KMS drivers,
> some people have considered porting Wayland as an experiment to see if it
> can work (I imagine the input driver support will be their first hurdle, but
> no where near as huge as getting a KMS driver into the kernel was).
It was, but over the past few weeks as I've been building the API I
want to expose, I've realised that there's just no way we can expose
everything the server needs. I've also not been great about
communicating that, but there's a README in the tree now which
explains stuff fairly well.
If an XKB2 ever happens, my rough plan is to bin the wire protocol and
just send the keymap over as one massive string. In that case,
clients can use libxkbcommon to parse the keymap and get a more
sensible keymap out, but not much we can do for the server.
Cheers,
Daniel
More information about the xorg-devel
mailing list