1. 29 Jul, 2019 6 commits
  2. 27 Jul, 2019 1 commit
  3. 25 Jul, 2019 4 commits
  4. 24 Jul, 2019 11 commits
  5. 23 Jul, 2019 10 commits
  6. 22 Jul, 2019 2 commits
    • Federico Mena Quintero's avatar
    • Ting-Wei Lan's avatar
      Allow building with gettext ≥ 0.20 · f6dfb716
      Ting-Wei Lan authored
      The use of AM_GNU_GETTEXT_VERSION in configure.ac instructs autopoint to
      copy po/Makefile.in.in from the exact gettext version. It is fine if the
      version of gettext installed on the system has the same minor version
      number with the requested version, but it fails if you have a newer
      version of gettext because of the mismatch between autoconf macros and
        *** error: gettext infrastructure mismatch: using a Makefile.in.in
        from gettext version 0.19 but the autoconf macros are from gettext
        version 0.20
      Instead of specifying the exact version with AM_GNU_GETTEXT_VERSION, we
      can use AM_GNU_GETTEXT_REQUIRE_VERSION to ask autopoint to simply use
      the gettext version installed on the system to prevent the mismatch.
  7. 21 Jul, 2019 1 commit
  8. 19 Jul, 2019 1 commit
    • Chun-wei Fan's avatar
      NMake Makefiles: Make gettext-runtime libname configurable · 624d6af3
      Chun-wei Fan authored
      Some people might be linking to gettext-runtime using intl.lib, while
      others might be using libintl.lib (such as vcpkg builds), depending on
      how gettext-runtime was built.  Add LIBINTL_LIB to the configurable
      items, which defaults to intl.lib, in the NMake Makefiles so that we
      can override it if needed in the NMake command line.
      See #485 (comment 556977) for a
      discussion on this.
  9. 16 Jul, 2019 2 commits
  10. 11 Jul, 2019 2 commits