1. 11 Jan, 2022 1 commit
  2. 28 Jul, 2021 1 commit
  3. 23 May, 2021 1 commit
    • John Ericson's avatar
      Make test suite work with cross-related options · f9c1b6f6
      John Ericson authored
      Because of skepticism I received in #224, I made this PR which keeps the
      testsuite and CI improvements but doesn't add any new build options. I
      hope this would be less controversial:
      
       - no new knobs
       - tests for those using existing build options
       - CI tests `build_introspection_data = false`
      f9c1b6f6
  4. 17 Jun, 2020 1 commit
    • Alexander Kanavin's avatar
      gir: add a dependency for g-ir-compiler for building .girs · 56ba5656
      Alexander Kanavin authored
      meson inserts the dependency if the compiler is used directly, but
      fails to do so if the compiler is run through a wrapper. This leads
      to build race errors between building the compiler and using it.
      
      Fix provided by Quentin Schulz <quentin.schulz@streamunlimited.com>
      56ba5656
  5. 17 May, 2020 1 commit
  6. 27 Apr, 2020 1 commit
    • John Ericson's avatar
      Don't override finding executables when using pre-built tools. · 0881b78b
      John Ericson authored
      Actually, we shouldn't really need this. We are building `native: false`
      binaries so when we look up a `native: true` binary the override should
      not apply. I've fixed this upstream in meson in
      https://github.com/NixOS/nixpkgs/pull/86080, though some backwards
      compatibility migration might be in order.
      
      In the meantime, we can make `gi_cross_use_host_gi` prevent the
      overrides from happening, which will achieve the desired behavior.
      
      Finally, this allows us to use `find_program` in `scanner_command`,
      unconditionally, letting the presence of the override dictate whether a
      freshly-built or pre-built `g-ir-scanner` is used.
      0881b78b
  7. 17 Jan, 2020 1 commit
  8. 15 Jan, 2020 1 commit
    • Chun-wei Fan's avatar
      Visual Studio builds: Use -utf-8 where available · ad937bca
      Chun-wei Fan authored
      This avoids compilation erroring out on C4819 (Unicode handling issue in the
      Visual Studio compiler), notably when running on Chinese, Japanese and Korean
      (CJK) locales.
      
      This also applies -utf-8 into the cflags passed into the various g-ir-scanner
      command lines that are used to generate the *.gir files, where -utf-8 is
      available, so that we don't get flooded with C4819 warnings during the
      build, and therefore avoid potential mishaps, as C4819 is a real warning that
      warngs us the code may be incorrectly built.
      ad937bca
  9. 13 Dec, 2019 2 commits
    • Alexander Kanavin's avatar
      meson: address review comments · 284b4c82
      Alexander Kanavin authored
      See here:
      !64
      
      
      
      Particularly, options are renamed to make it more readable and clear.
      Signed-off-by: Alexander Kanavin's avatarAlexander Kanavin <alex.kanavin@gmail.com>
      284b4c82
    • Alexander Kanavin's avatar
      meson_options.txt: add host-gi, gi-cross-wrapper, gi-ldd-wrapper,... · 1707d9b2
      Alexander Kanavin authored
      
      meson_options.txt: add host-gi, gi-cross-wrapper, gi-ldd-wrapper, introspection-data and pkgconfig-sysroot-path options
      
      With the first option, gobject-introspection tools (g-ir-doc-tool and g-ir-scanner)
      that are already installed in the host system will be used for building the source tree.
      
      With the second option, g-ir-scanner will be instructed to use an executable
      wrapper to run binaries it's producing, and g-ir-compiler will be run
      through the same wrapper (host system's g-ir-compiler cannot be used because
      it's producing architecture-specific output).
      
      With the third option, giscanner will be instructed to use a special ldd
      command instead of system's ldd (which does not work when the binary to inspect
      is compiled for a different architecture).
      
      With the fourth option, it is possible to disable building of introspection data
      (.gir and .typelib files), which may be difficult or impossible in cross-compilation
      environments, because of lack of emulation (or native hardware) for the target architecture
      on which the target binaries can be run.
      
      With the fifth option, paths returned by pkg-config are prefixed with the sysroot
      path (which is the destination path for cross-compiled items on the system where
      cross-compilation happens).
      
      These options are useful when cross-compiling for a different target architecture.
      Signed-off-by: Alexander Kanavin's avatarAlexander Kanavin <alex.kanavin@gmail.com>
      1707d9b2
  10. 27 Jul, 2019 1 commit
  11. 13 Jun, 2019 1 commit
  12. 03 Jun, 2019 1 commit
  13. 20 Apr, 2019 1 commit
  14. 07 Apr, 2019 1 commit
  15. 04 Mar, 2019 1 commit
  16. 07 Jan, 2019 1 commit
  17. 01 Jan, 2019 1 commit
  18. 16 Dec, 2018 1 commit
    • Christoph Reiter's avatar
      girepository: Add version macros and functions. Fixes #200 · 9c339f8b
      Christoph Reiter authored
      This adds the following macros and functions: GI_MAJOR_VERSION, GI_MICRO_VERSION,
      GI_MINOR_VERSION, GI_CHECK_VERSION, gi_get_major_version,gi_get_micro_version,
      gi_get_minor_version.
      
      Since we share a prefix with glib we have to namespace these by using the gi_
      prefix. g_gi would also work but we already export symbols with gi_ like
      gi_cclosure_marshal_generic(), gi_type_tag_get_ffi_type() and
      gi_type_info_extract_ffi_return_value(), so let's not add another naming scheme.
      9c339f8b
  19. 10 Dec, 2018 1 commit
  20. 08 Dec, 2018 1 commit
  21. 24 Nov, 2018 1 commit
  22. 09 Oct, 2018 1 commit
  23. 11 Jul, 2018 1 commit
  24. 15 May, 2018 1 commit
  25. 20 Apr, 2018 1 commit
  26. 10 Mar, 2018 13 commits