1. 14 Feb, 2017 1 commit
  2. 07 Feb, 2017 1 commit
  3. 27 Jan, 2017 1 commit
    • Pekka Paalanen's avatar
      wayland-server: hide wl_priv_signal from doxygen · 56f2dad6
      Pekka Paalanen authored
      Fix this set of warnings appearing three times during a build:
      
      /home/pq/git/wayland/src/wayland-server.c:1868: warning: class
      `wl_priv_signal' for related function `wl_priv_signal_init' is not
      documented.
      /home/pq/git/wayland/src/wayland-server.c:1884: warning: class
      `wl_priv_signal' for related function `wl_priv_signal_add' is not
      documented.
      /home/pq/git/wayland/src/wayland-server.c:1899: warning: class
      `wl_priv_signal' for related function `wl_priv_signal_get' is not
      documented.
      
      Our Wayland docbook don't include private things, so make sure these do
      not end up there. This removes the mention of wl_priv_signal_emit from
      the Server API docbook. I have no idea why the other functions did not
      appear there.
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: default avatarYong Bakos <ybakos@humanoriented.com>
      56f2dad6
  4. 26 Jan, 2017 2 commits
  5. 25 Jan, 2017 8 commits
  6. 24 Jan, 2017 6 commits
  7. 10 Dec, 2016 1 commit
  8. 28 Nov, 2016 1 commit
    • Yong Bakos's avatar
      doc: Remove wayland-util.c from file list · deb370cc
      Yong Bakos authored
      Documentation generation via doxygen includes wayland-util.c in its file
      list. Although functions are documented in wayland-util.h, doxygen is
      not automatically using the same documentation for functions in
      wayland-util.c. In addition, everything listed in the doxygen page for
      wayland-util.c is documented in the page for wayland-util.h and the
      pages for corresponding structures. As such, the doxygen page for
      wayland-util.c has no value, and is redundant.
      
      Remove the doxygen page for wayland-util.c.
      Signed-off-by: default avatarYong Bakos <ybakos@humanoriented.com>
      Acked-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      deb370cc
  9. 23 Nov, 2016 3 commits
    • Yong Bakos's avatar
      doc: Remove display of WL_PRINTF attribute · 20742b74
      Yong Bakos authored
      Doxygen truncates a WL_PRINTF function attribute, and there does not
      seem to be any workaround[1]. When using the attribute like this:
      
      typedef void (*wl_log_func_t)(const char *, va_list) WL_PRINTF(1, 0);
      
      Doxygen generates something that looks like this:
      
      typedef void (*wl_log_func_t)(const char *, va_list) WL_PRINTF(1,
      
      Configure doxygen to consider WL_PRINTF(x,y) as predefined, so it does
      not display the attribute at all in the generated documentation.
      
      [1] https://bugzilla.gnome.org/show_bug.cgi?id=774741Signed-off-by: default avatarYong Bakos <ybakos@humanoriented.com>
      Reviewed-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      20742b74
    • Pekka Paalanen's avatar
      tests: add scanner tests · c9f64544
      Pekka Paalanen authored
      Add tests that ensure that wayland-scanner output for a given input does
      not change unexpectedly. This makes it very easy to review
      wayland-scanner patches.
      
      Before, when patches were proposed for wayland-scanner, I had to
      build wayland without the patches, save the generated files into a
      temporary directory, apply the patches, build again, and diff the old
      vs. new generated file.
      
      No more. Now whenever someone makes intentional changes to
      wayland-scanner's output, he will also have to patch the example output
      files to match. That means that reviewers see the diff of the generated
      files straight from the patch itself. Verifying the diff is true is as
      easy as 'make check'.
      
      The tests use separate example XML files instead of wayland.xml
      directly, so that wayland.xml can be updated without fixing scanner
      tests, avoiding the churn.
      
      example.xml starts as a copy of wayland.xml. If wayland.xml starts using
      new wayland-scanner features, they should be copied into example.xml
      again to be covered by the tests.
      
      This patch relies on the previous patch to actually add all the data
      files for input and reference output.
      
      The scanner output is fed through sed to remove parts that are allowed
      to vary: the scanner version string.
      
      v2: no need for scanner-test.sh to depend on the test data
      
      Task: https://phabricator.freedesktop.org/T3313Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: Emilio Pozuelo Monfort <emilio.pozuelo@collabora.co.uk> (v1)
      Reviewed-by: default avatarYong Bakos <ybakos@humanoriented.com>
      Tested-by: default avatarYong Bakos <ybakos@humanoriented.com>
      c9f64544
    • Pekka Paalanen's avatar
      tests: add data files for future wayland-scanner test · 992b451d
      Pekka Paalanen authored
      This patch adds the input and reference output data files for the
      wayland-scanner tests to be added by the following patch.
      
      The data files are split into their own patch because they are extremely
      uninteresting to review:
      - example.xml is just a copy wayland.xml from 1.12.0
      - small.xml is a tiny dummy definition used for testing scanner
        variations without causing lots of big output files
      - the other files are wayland-scanner products from the xml files
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      Reviewed-by: default avatarEmilio Pozuelo Monfort <emilio.pozuelo@collabora.co.uk>
      v2: update output due to 2c6350beAcked-by: default avatarYong Bakos <ybakos@humanoriented.com>
      992b451d
  10. 21 Nov, 2016 9 commits
  11. 18 Nov, 2016 4 commits
  12. 17 Nov, 2016 1 commit
  13. 16 Nov, 2016 2 commits