- May 21, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We'll need those if we want to run ldconfig. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The entire setup for this call to `readlink -f` should have been removed when it was hoisted further up in bind_runtime() (and replaced with `readlink -e`) during commit 26b3be64, but in fact only the part that actually *ran* the wrapped readlink command was deleted. This also always leaked some memory. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
At the moment it writes to the current working directory, and we invoke it via `bwrap ... --chdir DIRECTORY`; but we want to make it possible to use this code from inside a Flatpak runtime (at least in the case where we're using the host system's glibc), which means we won't be allowed to run bwrap and must do this some other way. Rather than using `env --chdir=...` (which isn't supported in scout anyway), let's teach this script to output to an explicitly specified directory. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Previously we were missing coverage for this. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
While adding basic test coverage I discovered that this was not giving the intended answer if two values for the same variable appear in the environment block, which is rare but technically possible. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Now that it's in a static library, we can have some test coverage. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Unlike Autotools, in Meson this doesn't have the problems caused by recursive make: ninja always has an overview of the whole source tree. With this change, test-locale-gen.sh needs minor adjustments, because G_TEST_SRCDIR, G_TEST_BUILDDIR now point into tests/ instead of the root directory of the source tree. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This reduces repetition between pressure-vessel-wrap and pressure-vessel-with-lock, and will make it easier to test. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
There should be no practical effect except for repeating ourselves less. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We need this because older versions of G_STATIC_ASSERT worked by creating a dummy typedef, and didn't entirely suppress the resulting warnings. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We already (optionally) use --unshare-pid since commit feb948ed. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 20, 2020
-
-
Simon McVittie authored
Minor pressure-vessel-wrap fixes See merge request steam/pressure-vessel!44
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Use its own name, and not the first word of the command we executed or would have executed. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 19, 2020
-
-
Simon McVittie authored
runtime: Look for ldconfig in /sbin, /usr/sbin See merge request steam/pressure-vessel!43
-
- May 18, 2020
-
-
Simon McVittie authored
Build improvements See merge request steam/pressure-vessel!42
-
Simon McVittie authored
If we are on an OS where /sbin is not normally in unprivileged users' PATHs (for example Debian), we won't find ldconfig in PATH and will need to try harder. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We don't need any of these, so we might as well reduce dependencies and speed up the build a bit. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 05, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 15, 2020
-
-
Simon McVittie authored
Follow-ups for T12902 See merge request steam/pressure-vessel!41
-
Simon McVittie authored
We use the same GPtrArray to accumulate both i386 and x86_64 drivers, so ideally we allocate enough space for both and never have to reallocate it again. (But if we guess wrong, no harm done.) Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Even better than an assertion that crashes at runtime if we were wrong - an assertion that makes the build fail if we were wrong, so we can't release code where this assertion would fail. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Unlike EGL and Vulkan, we assign to these variables once per multiarch tuple, separately; so we need to free them once per multiarch tuple, too. Move their scope inwards so we can do that. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Bind VA-API drivers and loaders See merge request steam/pressure-vessel!35
-
If available, and newer, we bind VA-API drivers and loaders from the host system. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Simon McVittie authored
Bind VDPAU drivers See merge request steam/pressure-vessel!27
-
- Apr 09, 2020
-
-
Ludovico de Nittis authored
If available, and newer, we bind VDPAU drivers from the host system. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Apr 08, 2020
-
-
Simon McVittie authored
wrap: Add the ability to unshare the pid namespace See merge request steam/pressure-vessel!16
-
Simon McVittie authored
This improves isolation between the host system and the game, and can be used in conjunction with bwrap's init/reaper process to make game termination fully reliable (unlike subreapers, killing the init process automatically kills the entire pid namespace). One major down-side of doing this is that if the game uses process-ID-oriented APIs, for example older versions of <https://github.com/FeralInteractive/gamemode >, then they will not work, because the process ID inside the container is not the same as the process ID outside the container. Unfortunately, Steam's own tracking of the processes that belong to a game is one of the process-ID-oriented APIs that this harms, so this branch does not unshare the pid namespace by default, only when requested. We can use this to test whether it can be done without breaking Steam; We will probably need to cope with separate pid namespaces if we create new containers from inside a Flatpak environment. Also add an option to unload the gameoverlayrenderer.so module, which is not acceptable for production use, but at least works around this well enough to unblock further testing. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Apr 06, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-