- Dec 10, 2020
-
-
Simon McVittie authored
We are not going to be able to do this from within Flatpak, and it is unsuitable for running runtimes other than Steam Runtime 1 'scout', for which the LD_LIBRARY_PATH runtime mostly already works. If we need an automatic fallback to running on the host for scout games, we can do that better by running `pressure-vessel-wrap --test`. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 30, 2020
-
-
Ludovico de Nittis authored
In case a user is experiencing some problems he might try to disable the import of Vulkan layers to better isolate the issue he is facing. Fixes: #37 Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Nov 24, 2020
-
-
Simon McVittie authored
This provides a generic way to get OS-specific library directories, Vulkan layers' configuration, etc. into the container. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 01, 2020
-
-
Simon McVittie authored
pressure-vessel-wrap unsets PWD, but we don't want the command to inherit a value of PWD from the launcher. In particular, when running in session mode, the launcher's $PWD is the Steam installation, typically ~/.local/share/Steam, and the setup commands are also run with that working directory, but the actual game is run with the current working directory set to its own game directory (which we didn't necessarily even know at the time that the launcher was started). Consumers of $PWD should really check that it is equivalent to the actual current working directory and ignore it if it does not, like GNU get_current_dir_name(3) and our pv_get_current_dirs() do, but blindly believing $PWD is a common shell-scripting mistake, and I wouldn't be surprised if there are some games whose launcher scripts will believe $PWD even when it doesn't coincide with the real working directory. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 30, 2020
-
-
Ludovico de Nittis authored
In the future this option might be used to leverage some of the 'pressure-vessel-launcher' features, like locking specific environment variables. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Sep 09, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 08, 2020
-
-
Simon McVittie authored
Part of pressure-vessel#6. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This takes over responsibility from the shell scripts that currently wrap this executable. When combined with a Steam update, this should resolve a lot of issues involving paths outside the current working directory. Resolves: pressure-vessel#4 Resolves: pressure-vessel#11 Resolves: pressure-vessel#12 Resolves: https://github.com/ValveSoftware/steam-runtime/issues/217 Resolves: https://github.com/ValveSoftware/steam-runtime/issues/236 Resolves: https://github.com/ValveSoftware/steam-runtime/issues/257 Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 07, 2020
-
-
Simon McVittie authored
Recent versions of Steam set this when running setup commands in the context of a particular app, so that the setup commands can find their home directory if unsharing $HOME. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 19, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-