1. 22 Sep, 2016 1 commit
  2. 20 Sep, 2016 1 commit
  3. 13 Sep, 2016 1 commit
  4. 06 Sep, 2016 1 commit
  5. 30 Aug, 2016 1 commit
  6. 16 Aug, 2016 1 commit
  7. 01 Jun, 2016 2 commits
  8. 24 May, 2016 1 commit
  9. 18 May, 2016 1 commit
  10. 04 May, 2016 1 commit
  11. 29 Feb, 2016 1 commit
  12. 17 Feb, 2016 2 commits
  13. 16 Feb, 2016 1 commit
  14. 09 Feb, 2016 1 commit
  15. 02 Feb, 2016 1 commit
  16. 19 Jan, 2016 2 commits
  17. 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
  18. 22 Sep, 2015 1 commit
  19. 21 Sep, 2015 1 commit
  20. 16 Sep, 2015 1 commit
  21. 01 Sep, 2015 1 commit
  22. 16 Aug, 2015 1 commit
  23. 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: default avatarRoss Burton <ross.burton@intel.com>
      Reviewed-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      21f80b89
  24. 18 Jun, 2015 2 commits
  25. 03 Jun, 2015 1 commit
  26. 02 Jun, 2015 1 commit
  27. 27 May, 2015 1 commit
  28. 16 May, 2015 1 commit
  29. 07 May, 2015 1 commit
  30. 07 Apr, 2015 1 commit
  31. 18 Feb, 2015 1 commit
  32. 14 Feb, 2015 1 commit
  33. 07 Feb, 2015 1 commit
  34. 06 Feb, 2015 1 commit
  35. 31 Jan, 2015 1 commit
  36. 30 Jan, 2015 1 commit