1. 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
      missing.
      
      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>
      8011b0fa
  2. 11 Sep, 2018 1 commit
  3. 30 May, 2018 1 commit
  4. 18 Dec, 2017 4 commits
  5. 30 Jan, 2017 1 commit
    • Daniel Stone's avatar
      tests: Remove buffer-count · 4938f93f
      Daniel Stone authored
      buffer-count was introduced in line with a Mesa change which forced
      an earlier block on frame events to try to enforce double-buffering
      where available.
      
      The Mesa change has since been reverted (Mesa commit 9ca6711faa), as
      this had unpleasant interactions with buffer_age in particular, so this
      test is no longer valid.
      
      Additionally, it only worked on backends which initialised EGL (not
      headless-backend, where tests generally run), which can be flaky due to
      initialisation races. Not only that, but on the DRM backend, we can
      legitimately enter triple-buffering due to promoting the surface to a
      hardware plane, skipping GPU composition.
      
      In light of all this, just remove the test.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Reviewed-by: default avatarDerek Foreman <derekf@osg.samsung.com>
      4938f93f
  6. 03 Jan, 2017 1 commit
  7. 09 Jun, 2016 1 commit
  8. 29 Apr, 2016 1 commit
  9. 07 Mar, 2016 1 commit
  10. 19 Nov, 2015 9 commits
  11. 30 Sep, 2015 1 commit
    • Derek Foreman's avatar
      xdg-shell: Clarify ack_configure behaviour · dcba1a10
      Derek Foreman authored
      Right now many toolkits (toytoolkit, gtk+ and EFL) will send an
      ack_configure request immediately in response to a configure event,
      even if they're not immediately committing the surface at that time.
      
      This leads to a situation where multiple configures receive ack_configure
      before any commit happens.
      
      There's really no reason for that sequence of events to bother a compositor,
      so this just clarifies the language to make it ok.
      Signed-off-by: default avatarDerek Foreman <derekf@osg.samsung.com>
      Reviewed-by: Jasper St. Pierre's avatarJasper St. Pierre <jstpierre@mecheye.net>
      dcba1a10
  12. 14 Aug, 2015 1 commit
    • Pekka Paalanen's avatar
      protocol: add linux_dmabuf extension (v3) · 23ab7159
      Pekka Paalanen authored
      An experimental (hence the 'z' prefix) linux_dmabuf Wayland protocol
      extension for creating dmabuf-based wl_buffers in a generic manner.
      
      This does not include proper dmabuf metadata negotiation because
      there is no way to communicate all dmabuf constraints from the
      compositor to a client before-hand. The client has to create a
      wl_buffer wrapping one or more dmabuf buffers and then listen at
      the feedback object returned to know if the operation was successful.
      
      RFCv1 changes (after a first draft without code):
      - some renames of interfaces and argument, no semantic changes
      - added destructor protocol to dmabuf_batch
      - added feedback interface for buffer creation
      
      v2 changes:
      - use drm_fourcc.h as authoritative source for format codes
      - add support for the 64-bit layout qualifier and y-inverted dmabufs
      - simplify the 'add' request (no need to preserve fd numerical id)
      - add explicit plane index in the 'add' request
      - integrate the 'feedback' object events to the batch interface
      - rename 'create_buffer' to 'create' and move it into the batch interface
      - add requirements needed from the graphics stack and clients
      - improve existing errors and add batch error codes
      - removed error codes from the global interface
      - improve documentation for arguments, enums, etc.
      - rename dmabuf_batch to zlinux_buffer_params
      - The y-inverted property makes more sense as a whole buffer property.
        Y-flipping individual planes of the same buffer object is hardly useful.
        The y-invert is also converted into a flag, so we may add more flags
        later.
      - add flags for interlaced buffer content
      
      v3 changes:
      - Apply Daniel Vetter's comments about wording on coherency.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Signed-off-by: Louis-Francis Ratté-Boulianne's avatarLouis-Francis Ratté-Boulianne <lfrb@collabora.com>
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      Acked-by: Benjamin Gaignard's avatarBenjamin Gaignard <benjamin.gaignard@linaro.org>
      Reviewed-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      23ab7159
  13. 14 Jul, 2015 1 commit
  14. 26 Jun, 2015 2 commits
  15. 15 Jun, 2015 3 commits
  16. 22 May, 2015 4 commits
  17. 21 May, 2015 1 commit
  18. 12 May, 2015 1 commit
  19. 08 May, 2015 1 commit
  20. 05 May, 2015 4 commits