1. 29 Dec, 2020 1 commit
    • Eli Schwartz's avatar
      doc: make doxygen build from any directory · a023565e
      Eli Schwartz authored and Allan McRae's avatar Allan McRae committed
      In the autotools build, it only built in-tree, from cwd = doc/ and
      resolving doc/../lib/libalpm
      In the meson build, this accidentally worked if cwd =
      pacman/builddir/ and resolved to builddir/../lib/libalpm/
      But... this should always have been configured with the actual path to
      the inputs. So, we will now proceed to do so.
      Fixes building man3 if your out of tree builddir doesn't happen to be a
      direct subdirectory of the source root.
      Signed-off-by: Eli Schwartz's avatarEli Schwartz <eschwartz@archlinux.org>
      Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
  2. 21 Dec, 2020 1 commit
  3. 10 Feb, 2020 1 commit
  4. 28 May, 2019 1 commit
  5. 07 Mar, 2019 3 commits
  6. 16 Jan, 2019 1 commit
  7. 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.