1. 21 Sep, 2016 1 commit
  2. 01 Jun, 2016 1 commit
  3. 24 May, 2016 1 commit
  4. 18 May, 2016 1 commit
  5. 04 May, 2016 1 commit
  6. 29 Feb, 2016 1 commit
  7. 17 Feb, 2016 2 commits
  8. 16 Feb, 2016 1 commit
  9. 09 Feb, 2016 1 commit
  10. 02 Feb, 2016 1 commit
  11. 19 Jan, 2016 2 commits
  12. 17 Nov, 2015 1 commit
    • Peter Hutterer's avatar
      Validate the protocol xml during scanning · f66e2d53
      Peter Hutterer authored
      Embed the wayland.dtd protocol data into the scanner binary so we can validate
      external protocol files without requiring makefile changes. Hat-tip to Pekka
      Paalanen for the embedding trick.
      The embedding trick doesn't work well if the to-be-embedded file is in a
      different location than the source file, so copy/link it during configure and
      then build it in from the local directory.
      
      The current expat parser is not a validating parser, moving scanner.c to
      another parser has the risk of breaking compatibility. This patch adds libxml2
      as extra (optional) dependency, but that also requires parsing the input
      twice.
      
      If the protocol fails validation a warning is printed but no error is returned
      otherwise.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      f66e2d53
  13. 22 Sep, 2015 1 commit
  14. 21 Sep, 2015 1 commit
  15. 16 Sep, 2015 1 commit
  16. 01 Sep, 2015 1 commit
  17. 16 Aug, 2015 1 commit
  18. 17 Jul, 2015 1 commit
    • Ross Burton's avatar
      build: always build wayland-scanner · 21f80b89
      Ross Burton authored
      The previous idiom for building a cross-compiled Wayland is to build once for
      the build host (with --enable-scanner --disable-libraries) to get a
      wayland-scanner binary that can then be used in a cross-compile (with
      --disable-scanner).  The problem with this is that the cross wayland is missing
      a wayland-scanner binary, which means you then can't do any Wayland development
      on the target.
      
      Instead, always build wayland-scanner for the target and change
      --enable/disable-scanner to --with/without-host-scanner.  Normal builds use the
      default of --without-host-scanner and run the wayland-scanner it just built, and
      cross-compiled builds pass --with-host-scanner to use a previously built host
      scanner but still get a wayland-scanner to install.
      
      (a theoretically neater solution would be to build two scanners if required (one
      to run and one to install), but automake makes this overly complicated)
      
      [daniels: Bikeshedded naming with Ross's OK.]
      Signed-off-by: 's avatarRoss Burton <ross.burton@intel.com>
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      21f80b89
  19. 18 Jun, 2015 2 commits
  20. 03 Jun, 2015 1 commit
  21. 02 Jun, 2015 1 commit
  22. 27 May, 2015 1 commit
  23. 16 May, 2015 1 commit
  24. 07 May, 2015 1 commit
  25. 07 Apr, 2015 1 commit
  26. 18 Feb, 2015 1 commit
  27. 14 Feb, 2015 1 commit
  28. 07 Feb, 2015 1 commit
  29. 06 Feb, 2015 1 commit
  30. 31 Jan, 2015 1 commit
  31. 30 Jan, 2015 1 commit
  32. 29 Jan, 2015 2 commits
  33. 27 Jan, 2015 1 commit
  34. 17 Jan, 2015 1 commit
  35. 08 Dec, 2014 1 commit
  36. 22 Sep, 2014 1 commit
    • Peter Hutterer's avatar
      doc: replace publican with xmlto · f3e7eedf
      Peter Hutterer authored
      Publican isn't packaged for some distros, xmlto is a lot more common. Most of
      what publican provides for us is the stylesheet anyway, so we can just use
      xmlto and the publican stylesheet to get roughly the same look.
      
      PDF and XML generation has been dropped, this needs a bit more more effort
      than a mere switchover to xmlto.
      
      The top-level directory structure imposed by publican is kept for now
      (specifically the Wayland/en-US/html tree). This makes it easier to transition over
      for packagers. Note that the list of files inside has changed.
      
      CSS files are taken from publican to keep a uniform look compared to previous
      documentations. Stylesheets are licensed under CC0 1.0 Universal license, see
      publican/LICENSE:
      
      1.  Files in the datadir/Common_Content directory and its subdirectories are
          licensed under the CC0 1.0 Universal license.
      
          To the extent possible under law, the developers of Publican waive all
          copyright and related or neighboring rights to the files contained
          in the datadir/Common_Content directory and its subdirectories.
      Acked-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
      f3e7eedf