1. 16 Apr, 2019 1 commit
    • Adam Duskett's avatar
      Only build tests if certain conditions are met. · e7b0d89a
      Adam Duskett authored
      Currently, there is no way to prevent tests from building using meson.
      When cross-compiling, building the tests isn't necessary.
      Instead, only build the tests on the following conditions:
      1) If not cross-compiling.
      2) If cross-compiling, and there is an exe wrapper.
  2. 16 Mar, 2019 1 commit
    • Emmanuele Bassi's avatar
      Revert "headers: Add various missing G_DISABLE_DEPRECATED guards" · e5ba5845
      Emmanuele Bassi authored
      This reverts commit 80fcb1bc.
      G_DISABLE_DEPRECATED should never be used by anybody, least of all by
      GLib. We have deprecation annotations for the compiler, these days, and
      they are much better suited than a macro that makes symbols appear and
      disappear. The fact that gtk-doc doesn't understand the deprecation
      annotations is a limitation of gtk-doc, and it's gtk-doc that ought to be
      Commit 80fcb1bc broke GStreamer, which disables old API that was
      deprecated before the introduction of the deprecation annotations, but
      still uses newly deprecated one, and relies on the deprecation
      annotations to do their thing. It also broke libsoup, as it uses
      GValueArray in its own API.
  3. 15 Mar, 2019 2 commits
  4. 08 Mar, 2019 2 commits
  5. 07 Mar, 2019 1 commit
  6. 04 Mar, 2019 5 commits
  7. 28 Feb, 2019 1 commit
  8. 27 Feb, 2019 10 commits
  9. 22 Feb, 2019 3 commits
  10. 13 Feb, 2019 1 commit
    • Iain Lane's avatar
      installed tests: Allow tests to set environment variables · 07a1a803
      Iain Lane authored
      It's necessary sometimes for installed tests to be able to run with a
      custom environment. For example, the gsocketclient-slow test requires an
      LD_PRELOADed library to provide a slow connect() (this is to be added in
      a followup commit).
      Introduce a variable `@env@` into the installed test template, which we
      can override as necessary when generating `.test` files, to run tests
      prefixed with `/usr/bin/env <LIST OF VARIABLES>`.
      As the only test that requires this currently lives in `gio/tests/`, we
      are only hooking this up for that directory right now. If other tests in
      future require this treatment, then the support can be extended at that
  11. 01 Feb, 2019 1 commit
  12. 31 Jan, 2019 1 commit
  13. 25 Jan, 2019 1 commit
  14. 15 Jan, 2019 1 commit
    • Philip Withnall's avatar
      build: Drop autotools support · b3efef5b
      Philip Withnall authored
      So long, and thanks for everything. We’re a Meson-only shop now.
      glib-2-58 will remain the last stable GLib release series which is
      buildable using autotools.
      We continue to install autoconf macros for autotools-using projects
      which depend on GLib; they are stable API.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
  15. 27 Dec, 2018 1 commit
  16. 20 Dec, 2018 1 commit
    • Kouhei Sutou's avatar
      Suppress -Wint-in-bool-context warning with G_DEFINE_INTERFACE and g++ · b8ac6e14
      Kouhei Sutou authored
      Note that it's not reported with gcc. It's only reported with g++.
      C++ code to reproduce this warning:
          #include <glib-object.h>
          #define GARROW_TYPE_FILE (garrow_file_get_type())
          struct _GArrowFileInterface {
            GTypeInterface g_iface;
          static void
          garrow_file_default_init(GArrowFileInterface *iface)
      Build command line:
          % g++ -Wall -shared -o liba.so a.cpp $(pkg-config --cflags --libs gobject-2.0)
          In file included from /tmp/local.glib/include/glib-2.0/gobject/gobject.h:24,
                           from /tmp/local.glib/include/glib-2.0/gobject/gbinding.h:29,
                           from /tmp/local.glib/include/glib-2.0/glib-object.h:23,
                           from a.cpp:1:
          a.cpp: In function 'GType garrow_file_get_type()':
          /tmp/local.glib/include/glib-2.0/gobject/gtype.h:219:50: warning: '<<' in boolean context, did you mean '<' ? [-Wint-in-bool-context]
           #define G_TYPE_MAKE_FUNDAMENTAL(x) ((GType) ((x) << G_TYPE_FUNDAMENTAL_SHIFT))
          /tmp/local.glib/include/glib-2.0/gobject/gtype.h:2026:11: note: in definition of macro '_G_DEFINE_INTERFACE_EXTENDED_BEGIN'
                 if (TYPE_PREREQ) \
          /tmp/local.glib/include/glib-2.0/gobject/gtype.h:1758:47: note: in expansion of macro 'G_DEFINE_INTERFACE_WITH_CODE'
           #define G_DEFINE_INTERFACE(TN, t_n, T_P)      G_DEFINE_INTERFACE_WITH_CODE(TN, t_n, T_P, ;)
          a.cpp:16:1: note: in expansion of macro 'G_DEFINE_INTERFACE'
          /tmp/local.glib/include/glib-2.0/gobject/gtype.h:178:25: note: in expansion of macro 'G_TYPE_MAKE_FUNDAMENTAL'
           #define G_TYPE_OBJECT   G_TYPE_MAKE_FUNDAMENTAL (20)
          a.cpp:18:20: note: in expansion of macro 'G_TYPE_OBJECT'
  17. 17 Dec, 2018 1 commit
    • Benjamin Berg's avatar
      binding: Clarify the use of g_object_unref() to remove a binding · f5e1e169
      Benjamin Berg authored
      Conceptually the binding is kept alive as long as both the source and
      target exist. This means that an API user needs to take some care to
      either hold a reference or only use a pointer to the binding as long as
      also holding references to both objects.
      Clarify the documentation a bit.
  18. 12 Dec, 2018 3 commits
  19. 10 Dec, 2018 2 commits
  20. 05 Dec, 2018 1 commit