GitLab

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This makes it a lot easier to satisfy the build-dependencies on OSs
where GLib is not fully multiarch, like Debian 8 'jessie' and
SteamOS 2 'brewmaster'.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

We aren't building plugins for perl.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

$(patsubst) doesn't work here, breaking distcheck.
Signed-off-by: Simon McVittie <smcv@collabora.com>

If we are building from a tarball then we don't need it, because
autogen.sh copies all required macros into m4/.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This is necessary when cross-compiling, at least on Debian 8 'jessie'.
Signed-off-by: Simon McVittie <smcv@collabora.com>

The shared library could conceivably get linked into something at a
privilege boundary, but the tools have no such requirement. This
means we can reduce our glibc dependencies when not building the actual
library.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This is useful if you want to bundle a complete dependency stack but
use the host libc, like the Steam Runtime has traditionally done.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

We have to do this in two stages, because passing ${ORIGIN} through
Autoconf, Automake and Make is a massive pain: first write in a
dummy rpath that starts with /_ORIGIN_ (implemented here), then
rewrite it to start with ${ORIGIN} with chrpath (to be done
externally).
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

This should make it a little less confusing to work out what we're
looking at.
Signed-off-by: Simon McVittie <smcv@collabora.com>

This simplifies the situation by only needing one extra directory in
the LD_LIBRARY_PATH.
Signed-off-by: Simon McVittie <smcv@collabora.com>

If we mount the standalone GL stack at /run/host/$host_path and
make the library filenames be symlinks to there, then it's
immediately obvious from looking at the symlink which GL stack we're
using.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

If we capture the NVIDIA driver and all its dependencies, then we
have to use the equivalent of --libc-provider=auto, because its
dependencies include libc but ld.so has to be in lockstep with libc.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

In particular this is enough to capture the dependencies of the
Mesa DRI drivers:

    $ capsule-capture-libs --dest=lib \
      only-dependencies:path-match:"/usr/lib/x86_64-linux-gnu/dri/*.so"
    $ ls lib
    libbsd.so.0
    libc.so.6
    libdl.so.2
    libdrm_amdgpu.so.1    # etc.

and the drivers themselves:

    $ capsule-capture-libs --dest=mesa-drivers \
      no-dependencies:path-match:"/usr/lib/x86_64-linux-gnu/dri/*.so"
    $ ls mesa-drivers
    i915_dri.so   # etc.

in separate batches.
Signed-off-by: Simon McVittie <smcv@collabora.com>

For Mesa DRI drivers, we will need to capture the dependencies but
not the driver itself, because we load the driver itself by setting
LIBGL_DRIVERS_PATH instead.

I don't have a concrete use-case for no-dependencies:, which is
implemented for symmetry.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

We still do this for unadorned wildcards, but explicit is better than
implicit.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

We can set needed[0] to the absolute path to a loadable module, and
in fact we will need to do that when collecting the dependencies
of a Mesa DRI driver.
Signed-off-by: Simon McVittie <smcv@collabora.com>

Previously, we just used strrchr(), but that didn't actually return
the basename as in basename(1): we were comparing strings like
"/libc-2.17.so" or "/libglib-2.0.so.0.5600.0".
Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>

Signed-off-by: Simon McVittie <smcv@collabora.com>