1. 02 Apr, 2018 1 commit
  2. 10 Oct, 2017 1 commit
  3. 26 Apr, 2017 1 commit
    • Eric Anholt's avatar
      Add a Meson build system alongside autotools. · 1549e303
      Eric Anholt authored
      This is a work in progress that builds Xvfb, Xephyr, Xwayland, Xnest,
      and Xdmx so far.  The outline of Xquartz/Xwin support is in tree, but
      hasn't been built yet.  The unit tests are also not done.
      The intent is to build this as a complete replacement for the
      autotools system, then eventually replace autotools.  meson is faster
      to generate the build, faster to run the bulid, shorter to write the
      build files in, and less error-prone than autotools.
      v2: Fix indentation nits, move version declaration to project(), use
          existing meson_options for version-config.h's vendor name/web.
      Signed-off-by: Eric Anholt's avatarEric Anholt <eric@anholt.net>
      Acked-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Reviewed-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  4. 01 Mar, 2017 1 commit
  5. 21 Apr, 2015 1 commit
  6. 09 Dec, 2014 2 commits
  7. 12 Nov, 2014 1 commit
  8. 12 Jan, 2014 1 commit
  9. 10 Sep, 2013 3 commits
  10. 10 Jul, 2012 3 commits
  11. 21 Mar, 2012 2 commits
    • Daniel Stone's avatar
      Indentation: Change '& stuff' to '&stuff' · ab3a815a
      Daniel Stone authored
      If the typedef wasn't perfect, indent would get confused and change:
          foo = (SomePointlessTypedef *) &stuff[1];
          foo = (SomePointlessTypedef *) & stuff[1];
      Fix this up with a really naïve sed script, plus some hand-editing to
      change some false positives in XKB back.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
    • Keith Packard's avatar
      Introduce a consistent coding style · 9838b703
      Keith Packard authored
      This is strictly the application of the script 'x-indent-all.sh'
      from util/modular. Compared to the patch that Daniel posted in
      January, I've added a few indent flags:
      	-T PrivatePtr
      	-T pmWait
      	-T _X_EXPORT
      The typedefs were needed to make the output of sdksyms.sh match the
      previous output, otherwise, the code is formatted badly enough that
      sdksyms.sh generates incorrect output.
      The generated code was compared with the previous version and found to
      be essentially identical -- "assert" line numbers and BUILD_TIME were
      the only differences found.
      The comparison was done with this script:
      for dir in $dir1 $dir2; do
      	(cd $dir && find . -name '*.o' | while read file; do
      		dir=`dirname $file`
      		base=`basename $file .o`
      		objdump -d $file > $dump
      find $dir1 -name '*.dump' | while read dump; do
      	otherdump=`echo $dump | sed "s;$dir1;$dir2;"`
      	diff -u $dump $otherdump
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
      Acked-by: Daniel Stone's avatarDaniel Stone <daniel@fooishbar.org>
      Acked-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
  12. 23 Sep, 2011 1 commit
  13. 21 Sep, 2011 1 commit
  14. 03 May, 2011 1 commit
  15. 02 Jul, 2010 2 commits
  16. 10 Jun, 2010 1 commit
  17. 06 Jun, 2010 3 commits
  18. 03 Jun, 2010 1 commit
    • Aaron Plattner's avatar
      Fix pixmap validation in miDbePositionWindow. · 1304b8b2
      Aaron Plattner authored
      miDbePositionWindow allocates two pixmaps: a front buffer, and a back buffer.
      If the buffers are supposed to be initialized, it validates a GC against the
      front buffer, then uses it to fill and/or copy both the front buffer *and* the
      back buffer, without revalidating.  If the acceleration architecture needs
      different GC funcs for the two pixmaps -- for example if allocation of the front
      buffer exhausted video memory -- then this can cause crashes because the GC is
      not validated for the back buffer pixmap.
      Fix this by performing the rendering for the front buffer first, then
      revalidating against the back buffer before performing the back buffer
      Signed-off-by: Aaron Plattner's avatarAaron Plattner <aplattner@nvidia.com>
      Reviewed-by: Jamey Sharp's avatarJamey Sharp <jamey@minilop.net>
      Signed-off-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
  19. 19 May, 2010 1 commit
  20. 16 May, 2010 1 commit
  21. 14 May, 2010 2 commits
  22. 13 May, 2010 1 commit
    • Jamey Sharp's avatar
      Kill DoChangeGC in favor of dixChangeGC. · 65cedf39
      Jamey Sharp authored
      This doesn't change any behavior, but it isn't clear whether NullClient
      is correct in all cases. As ajax says,
      > For most of these changes, I think it's correct to use NullClient,
      > since they are server-initiated changes and should not fail for (eg)
      > xace reasons. ... At any rate, you're certainly not changing any
      > semantics by leaving them all as NullClient, so this patch can't be
      > more wrong than before.
      Signed-off-by: Jamey Sharp's avatarJamey Sharp <jamey@minilop.net>
      Reviewed-by: Keith Packard's avatarKeith Packard <keithp@keithp.com>
  23. 12 May, 2010 1 commit
  24. 19 Dec, 2009 3 commits
  25. 17 Jul, 2009 2 commits
  26. 14 Jul, 2009 1 commit
  27. 29 Apr, 2009 1 commit