1. 13 Jul, 2017 2 commits
    • Nirbheek Chauhan's avatar
      meson: Improve MSVC and MinGW support and fix dependencies everywhere · fe2a9887
      Nirbheek Chauhan authored
      Disable gio tests on Windows, fix .gitignore to not ignore
      config.h.meson, and add more things to it.
      
      Rename the library file naming and versioning to match what Autotools
      outputs, e.g., libglib-2.0.so.0.5000.2 on Linux, libglib-2.0-0.dll  and
      glib-2.0-0.dll on Windows with MSVC.
      
      Several more tiny fixes, more executables built and installed, install
      pkg-config and m4 files, fix building of gobject tests.
      
      Changes to gdbus-codegen to support out-of-tree builds without
      environment variables set (which you can't in Meson). We now add the
      build directory to the Python module search path.
      fe2a9887
    • Tim-Philipp Müller's avatar
      meson: Fix glib, add gobject, gio, gthread, gmodule, etc · 21395797
      Tim-Philipp Müller authored
      Several small fixes to the build files.
      
      Lots of tests have also been added, and glib tests pass now.
      21395797
  2. 09 Mar, 2017 1 commit
    • Steven McDonald's avatar
      gio: Always purge kqueue subs from missing list · e305fe97
      Steven McDonald authored
      Previously, _kh_cancel_sub assumed that it only needed to call
      _km_remove if sub did not exist in subs_hash_table. This is erroneous
      because the complementary operation, _km_add_missing, can be called
      from process_kqueue_notifications, in which context sub can *only* have
      come from subs_hash_table.
      
      Since _km_remove is implemented using g_slist_remove, which is
      documented to be a noop if the list does not contain the element to be
      removed, it is safe to call _km_remove unconditionally here.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=778515
      e305fe97
  3. 05 Jun, 2015 1 commit
  4. 20 Mar, 2015 1 commit
  5. 05 Feb, 2015 1 commit
  6. 18 Aug, 2014 1 commit
  7. 01 Feb, 2014 1 commit
  8. 26 Dec, 2013 1 commit
  9. 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
  10. 21 May, 2013 1 commit
    • Dan Winship's avatar
      Use 'dumb quotes' rather than `really dumb quotes' · 4b94c083
      Dan Winship authored
      Back in the far-off twentieth century, it was normal on unix
      workstations for U+0060 GRAVE ACCENT to be drawn as "‛" and for U+0027
      APOSTROPHE to be drawn as "’". This led to the convention of using
      them as poor-man's ‛smart quotes’ in ASCII-only text.
      
      However, "'" is now universally drawn as a vertical line, and "`" at a
      45-degree angle, making them an `odd couple' when used together.
      
      Unfortunately, there are lots of very old strings in glib, and also
      lots of new strings in which people have kept up the old tradition,
      perhaps entirely unaware that it used to not look stupid.
      
      Fix this by just using 'dumb quotes' everywhere.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=700746
      4b94c083
  11. 18 Jan, 2013 1 commit
    • Allison Karlitskaya's avatar
      Fix visibility for glib/ and gio/ submodules · 346aa683
      Allison Karlitskaya authored
      We have various sub directories in glib/ and gio/ (eg: inotify, gnulib,
      pcre, xdgmime, etc.) that build convenience libraries that are then
      included into libglib and libgio.  The files in these directories need
      to be built with the same visibility policy as the files in the first
      level directories, so add CFLAGS for them all.
      
      This wasn't a problem when the visibility flags were set directly in
      CFLAGS but then we had to deal with some modules that we built that we
      explicitly wanted to export symbols from.
      
      For now, we can keep things the way they are because it's less hacky and
      although it's a theoretical hazard to forget these CFLAGS, we rarely add
      new subdirectories to the build.
      346aa683
  12. 14 Jan, 2013 1 commit
  13. 17 Nov, 2012 1 commit
  14. 15 Nov, 2012 1 commit