1. 18 Dec, 2018 4 commits
  2. 15 Dec, 2018 1 commit
  3. 09 Dec, 2018 1 commit
    • Daniel Stone's avatar
      Add Meson build system · 8011b0fa
      Daniel Stone authored
      Meson is a build system, currently implemented in Python, with multiple
      output backends, including Ninja and Make. The build file syntax is
      clean and easy to read unlike autotools. In practise, configuring and
      building with Meson and Ninja has been observed to be much faster than
      with autotools. Also cross-building support is excellent.
      More information at http://mesonbuild.com
      Since moving to Meson requires some changes from users in any case, we
      took this opportunity to revamp build options. Most of the build options
      still exist, some have changed names or more, and a few have been
      dropped. The option to choose the Cairo flavour is not implemented since
      for the longest time the Cairo image backend has been the only
      recommended one.
      This Meson build should be fully functional and it installs everything
      an all-enabled autotools build does. Installed pkg-config files have
      some minor differences that should be insignificant. Building of some
      developer documentation that was never installed with autotools is
      It is expected that the autotools build system will be removed soon
      after the next Weston release.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Co-authored-by: Pekka Paalanen's avatarPekka Paalanen <pq@iki.fi>
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pq@iki.fi>
  4. 04 Dec, 2018 1 commit
  5. 20 Nov, 2018 5 commits
  6. 03 Nov, 2018 1 commit
  7. 02 Nov, 2018 2 commits
  8. 30 Oct, 2018 4 commits
  9. 18 Oct, 2018 2 commits
  10. 23 Sep, 2018 4 commits
  11. 18 Sep, 2018 4 commits
  12. 17 Sep, 2018 6 commits
  13. 11 Sep, 2018 1 commit
  14. 31 Aug, 2018 1 commit
  15. 20 Aug, 2018 1 commit
  16. 17 Aug, 2018 2 commits
    • Derek Foreman's avatar
      input: Send unique keymap file descriptors to clients · 76829fc4
      Derek Foreman authored
      Client may map any file descriptor opened for writing with PROT_WRITE
      themselves.  On linux, even a read-only file descriptor to an unlinked
      file can be re-opened with write permission through /proc/self/fd.
      The only way to prevent this is to create a memfd which
      is subsequently write-sealed.  Unfortunately this prevents clients
      from mapping with MAP_SHARED, which is already in widespread usage.
      To isolate and protect the keymap, whilst allowing MAP_SHARED clients
      to continue to work, use a unique file descriptor for each
      wl_keyboard resource.
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
    • Derek Foreman's avatar
      input: add weston_keyboard_send_keymap helper function · f8f7fd69
      Derek Foreman authored
      We've always had "send_keymap" internally, but some places failed to use
      it.  Since we also use this in the text backend, export it.
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>