1. 07 Oct, 2019 1 commit
    • Eli Schwartz's avatar
      Support file with seccomp enabled · de6249ce
      Eli Schwartz authored and Allan McRae's avatar Allan McRae committed
      Not all compression types can be detected in the seccomp sandbox, so we
      need to disable it. This requires either configuring makepkg to know the
      sandbox is available, or checking for file >= 5.38 in which the sandbox
      option is a no-op even when seccomp is disabled.
      - Requires autoconf-archive for autotools version compare macro.
      - meson version comparison could be made a lot simpler using meson-git.
      Fixes FS#58626
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
  2. 28 Jun, 2019 1 commit
  3. 19 Mar, 2019 1 commit
  4. 04 Feb, 2019 1 commit
  5. 02 Nov, 2018 1 commit
    • Dave Reisner's avatar
      Add meson.build files to build with meson · 51db8475
      Dave Reisner authored
      Provide both build systems in parallel for now, to ensure that we work
      out all the differences between the two. Some time from now, we'll give
      up on autotools.
      Meson tends to be faster and probably easier to read/maintain. On my
      machine, the full meson configure+build+install takes a little under
      half as long as a similar autotools-based invocation.
      Building with meson is a two step process. First, configure the build:
        meson build
      Then, compile the project:
        ninja -C build
      There's some mild differences in functionality between meson and
      autotools.  specifically:
      1) No singular update-po target. meson only generates individual
      update-po targets for each textdomain (of which we have 3).  To make
      this easier, there's a build-aux/update-po script which finds all
      update-po targets and runs them.
      2) No 'make dist' equivalent. Just run 'git archive' to generate a
      suitable tarball for distribution.