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.
      e7b0d89a
  2. 04 Mar, 2019 1 commit
  3. 01 Feb, 2019 1 commit
  4. 10 Dec, 2018 2 commits
  5. 25 Nov, 2018 1 commit
  6. 22 Oct, 2018 1 commit
  7. 19 Jul, 2018 2 commits
    • Christoph Reiter's avatar
      meson: use the new 'python' module instead of the 'python3' one. Closes #1455 · 631c3534
      Christoph Reiter authored
      The new python module, added with 0.46, works with Python 2 and 3 and
      allows to pass a path for the interpreter to use, if the need arises.
      
      Previously the meson build set PYTHON, used in the shebang line of
      the scripts installed by glib, to the full path of the interpreter.
      The new meson module doesn't expose that atm, but we should set it to
      a executable name anyway, and not a full path.
      631c3534
    • Nirbheek Chauhan's avatar
      meson: Provide our Python tools for builds · 057f393b
      Nirbheek Chauhan authored
      Several of our tools are installed and are used by other projects to
      generate code. However, there is no 'install' when projects use glib
      as a subproject.
      
      We need some way for glib to 'provide' these tools so that when some
      project uses glib as a subproject, find_program('glib-mkenums') will
      transparently return the glib-mkenums we just built.
      
      Starting from Meson 0.46, this can be done with the
      `meson.override_find_program()` function.
      
      As a bonus, the Meson GNOME module will also use these
      'overriden'/'provided' programs instead of looking for them in PATH.
      057f393b
  8. 15 May, 2018 1 commit
  9. 09 May, 2018 1 commit
  10. 28 Mar, 2018 1 commit
  11. 21 Feb, 2018 1 commit
  12. 04 Jan, 2018 2 commits
  13. 22 Nov, 2017 1 commit
  14. 02 Nov, 2017 3 commits
  15. 11 Oct, 2017 1 commit
  16. 14 Sep, 2017 1 commit
    • Chun-wei Fan's avatar
      meson: Install items according to their relevance · a7a6449f
      Chun-wei Fan authored
      The m4 and bash completion items are usable and relevant
      depending on the host system's configuration.  So, we check for the
      presence of the programs that these items depend on, and only install
      them when those programs are found.
      
      For the Valgrind suppression files, we don't install them on Windows as
      Valgrind is currently not supported on Windows.
      
      Als fix the path where the GDB helpers are installed, as the path is
      incorrectly constructed.
      
      This will fix the "install" stage when building on Visual Studio at
      least as there are some post-install steps that are related to them,
      which will make use of these programs.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=783270
      a7a6449f
  17. 17 Jul, 2017 1 commit
    • Emmanuele Bassi's avatar
      meson: Simplify the use of built tools · 3c03cc8f
      Emmanuele Bassi authored
      The Meson build has fallen a bit behind the Autotools one, when it comes
      to the internally built tools like glib-mkenums and glib-genmarshals.
      
      We don't need to generate gmarshal.strings any more, and since the
      glib-genmarshal tool is now written in Python it can also be used when
      cross-compiling, and without indirection, just like we use glib-mkenums.
      
      We can also coalesce various rules into a simple array iteration, with
      minimal changes to glib-mkenums, thus making the build a bit more
      resilient and without unnecessary duplication.
      3c03cc8f
  18. 15 Jul, 2017 1 commit
  19. 14 Jul, 2017 1 commit
  20. 13 Jul, 2017 11 commits