Auke Booij

Here's one attempt at encoding a `display::error` message. You can run the following by saving it as `script.hs` (or whatever) and executing `stack script.hs`. ```haskell #!/usr/bin/env stack {- stack script...

The advantage of the above approach over C's approach of generating appropriate function stubs is that it allows to write type-safe code that is generic in the actual message being...

Upon further investigation, it seems that two points of my review are ill-informed: you're just using store's own approach to implementing a `Store` instance for `ByteString`, and the list instance...

`weston-simple-dmabuf-v4l` and `weston-simple-egl` run smoothly, so there is probably no immediate cause for concern.

The major omissions in CABI.Client are an analogue of libwayland's `display_fatal_error` (fired on e.g. read/write errors) and `display_protocol_error` (fired when we have received a wl_display.error message).

Commits d09d392 and c776e60 should partially resolve this. Can anyone watching this project comment on the progress on this bug? Is it easy to build, and does it work correctly?

Thanks for your feedback. The warning should be fixed now. I'm not sure how to make this run under stack - to be honest I'm not even sure why it...

Hi @xavier83, Forget about the cabal thing. Could you try adding the following to the provided stack.yaml ``` ghc-options: sudbury: -lHSrts-ghc7.10.3 ``` and trying the following ``` $ stack clean...

Thanks. Yes, that is WIP. Currently that bug actually functions as a feature since it indicates that sudbury is used rather than libwayland.

Some people are working on getting Cabal to build shared libraries. That would be excellent for us. See haskell/cabal#141