1. 26 Oct, 2017 2 commits
  2. 03 Apr, 2017 1 commit
  3. 11 Jan, 2016 1 commit
  4. 10 Jan, 2016 1 commit
  5. 09 Jan, 2016 1 commit
  6. 23 Dec, 2013 1 commit
  7. 20 Nov, 2013 1 commit
  8. 18 Nov, 2013 1 commit
  9. 07 Nov, 2013 1 commit
  10. 01 Jun, 2013 1 commit
    • Allison Karlitskaya's avatar
      Rework the build system for a new tests approach · f9eb9eed
      Allison Karlitskaya authored
      Perform a substantial cleanup of the build system with respect to
      building and installing testcases.
      
      First, Makefile.decl has been renamed glib.mk and substantially
      expanded.  We intend to add more stuff here in the future, like canned
      rules for mkenums, marshallers, resources, etc.
      
      By default, tests are no longer compiled as part of 'make'.  They will
      be built when 'make check' is run.  The old behaviour can be obtained
      with --enable-always-build-tests.
      
      --disable-modular-tests is gone (because tests are no longer built by
      default).  There is no longer any way to cause 'make check' to be a
      no-op, but that's not very useful anyway.
      
      A new glibtests.m4 file is introduced.  Along with glib.mk, this
      provides for consistent handling of --enable-installed-tests and
      --enable-always-build-tests (mentioned above).
      
      Port our various test-installing Makefiles to the new framework.
      
      This patch substantially improves the situation in the toplevel tests/
      directory.  Things are now somewhat under control there.  There were
      some tests being built that weren't even being run and we run those now.
      The long-running GObject performance tests in this directory have been
      removed from 'make check' because they take too long.
      
      As an experiment, 'make check' now runs the testcases on win32 builds,
      by default.  We can't run them under gtester (since it uses a pipe to
      communicate with the subprocess) so just toss them in TESTS.  Most of
      them are passing on win32.
      
      Things are not quite done here, but this patch is already a substantial
      improvement.  More to come.
      f9eb9eed
  11. 15 May, 2013 1 commit
  12. 02 Nov, 2012 1 commit
  13. 13 Jan, 2012 1 commit
  14. 04 Oct, 2011 1 commit
    • Antoine Jacoutot's avatar
      Fix DATADIRNAME on OpenBSD. · 8f58c2c0
      Antoine Jacoutot authored
      On OpenBSD translation files are always installed under PREFIX/share/locale,
      there is no such thing as PREFIX/lib/locale; according to that, set
      DATADIRNAME to "share".
      8f58c2c0
  15. 16 May, 2011 1 commit
  16. 31 Mar, 2011 1 commit
  17. 12 Dec, 2010 1 commit
  18. 04 Nov, 2010 1 commit
  19. 26 Oct, 2010 1 commit
    • Allison Karlitskaya's avatar
      gsettings m4: Use --strict for checking · 9126f1af
      Allison Karlitskaya authored
      A while ago we allowed glib-compile-schemas to return a 'success' status
      in the case that just one schema file contained errors.  Of course, this
      is the exact opposite of what we want in the case that we are checking
      schema validity at compile time.
      
      Use the --strict flag for that case.
      
      This closes #633115.
      9126f1af
  20. 04 Oct, 2010 1 commit
    • Allison Karlitskaya's avatar
      Bug 627126 - gsettings schemas on FreeBSD · 136e705e
      Allison Karlitskaya authored
      Rewrite the install rule for GSettings schemas to not depend on an
      obscure chunk of non-portable sed that nobody understands the purpose
      of.
      
      Instead, use make's VPATH feature to resolve the paths of the files that
      need to be installed.  No need to depend on the .valid targets here
      since automake already ensures that 'make all' is complete before 'make
      install' is permitted to run.
      136e705e
  21. 23 Sep, 2010 1 commit
  22. 03 Aug, 2010 1 commit
  23. 13 Jul, 2010 1 commit
  24. 30 Jun, 2010 1 commit
  25. 28 Jun, 2010 1 commit
    • Allison Karlitskaya's avatar
      Bug 622565 - compile-schemas fails when no schemas · 8a7d9906
      Allison Karlitskaya authored
      Neutralise and deprecate the --uninstall option in the schema compiler
      and remove it from gsettings.m4.
      
      Make the new default behaviour a compromise between the old default
      behaviour and the previous --uninstall option:
      
        - never return a failure code if no schema files are found
      
        - issue a warning instead
      
        - remove the gschemas.compiled file if it exists
      8a7d9906
  26. 19 Jun, 2010 1 commit
  27. 15 Jun, 2010 1 commit
  28. 27 May, 2010 1 commit
    • Allison Karlitskaya's avatar
      gsettings m4: check for .xml in src/builddir · b3593693
      Allison Karlitskaya authored
      This checks for the .gschema.xml file in the srcdir and builddir and
      runs the schema validation on which one it finds.  This handles
      non-srcdir builds in both cases: .gschema.xml is in the tarball and
      .gschema.xml is generated.
      b3593693
  29. 22 May, 2010 1 commit
  30. 19 May, 2010 2 commits
  31. 15 May, 2010 2 commits
    • Christian Persch's avatar
      Use the new option name · 63d74caa
      Christian Persch authored
      It's --schema-file now, not --schema-files.
      Bug #616864.
      63d74caa
    • Matthias Clasen's avatar
      Fix issues with GSETTINGS_CHECK_RULE · 2ed13de1
      Matthias Clasen authored
      Rename the --schema-files option to --schema-file, since it only
      accepts one file at a time. Change the GSETTINGS_CHECK_RULE to
      use it that way, too. And also make it work better with !srcdir
      builds.
      
      Bugs #616731 and #616864
      2ed13de1
  32. 09 May, 2010 1 commit
  33. 23 Apr, 2010 2 commits
  34. 21 Apr, 2010 2 commits
  35. 03 Nov, 2009 1 commit