Thanks Nikolay, that was the problem. SHENZHEN I/O has a launcher script
with the line
export LD_LIBRARY_PATH=$STEAM_LD_LIBRARY_PATH
I replaced that with
export LD_LIBRARY_PATH="$STEAM_LD_LIBRARY_PATH:$LD_LIBRARY_PATH"
and everything is working fine now.
On Mon, Dec 12, 2016 at 11:15
On 12/12/2016 11:28 PM, Mike Cooper wrote:
> Unfortunately, it didn't seem to have worked. I tried adding mesa, which
> seems to contain the missing library) to each of commonTargetPkgs and
> multipkgs in turn, but neither makes the error when launching the game
> go away.
You should never need
I am using NixOS, and I already have those configuration options set.
On Mon, Dec 12, 2016 at 10:34 AM Freddy Rietdijk
wrote:
> Are you on NixOS? If so, did you add
>
> hardware.opengl = { driSupport = true; driSupport32Bit = true; };
>
> On Mon, Dec 12, 2016 at 9:28
Are you on NixOS? If so, did you add
hardware.opengl = { driSupport = true; driSupport32Bit = true; };
On Mon, Dec 12, 2016 at 9:28 PM, Mike Cooper wrote:
> Thanks for the replies everyone. As for the meta issue, I think that
> having a steam package that is compatible with
On 09/12/16 10:45, Nikolay Amiantov wrote:
To clarify: I was talking not about Steam Runtime (the guaranteed set)
but rather extra libraries that some games need (a small set defined in
`multiPkgs`, under "Not formally in runtime but needed by some games"
comment). Removing something from the
To clarify: I was talking not about Steam Runtime (the guaranteed set)
but rather extra libraries that some games need (a small set defined in
`multiPkgs`, under "Not formally in runtime but needed by some games"
comment). Removing something from the runtime seems a bad idea to me.
On 12/09/2016
On 09/12/16 10:02, Nikolay Amiantov wrote:
I'm not sure if we want to add something like `extraDependencies`
argument to Steam; it feels better to me to just add those libraries
unconditionally so that games work out of the box (you don't expect
Steam to have low storage requirements anyway).
If you would move certain libraries out because of whatever reason, then I
think we need to introduce a set that defines per game the extra libraries
and introduce something like a steam.withGameLibs.
On Fri, Dec 9, 2016 at 11:07 AM, Nikolay Amiantov wrote:
> commonTargetPkgs is
commonTargetPkgs is not the right place for this: it's for binaries (not
libraries) that are needed both for steam-env and steam. Difference
between targetPkgs (binaries) and multiPkgs (libraries) is that latter
are installed for both architectures on 64-bit systems; you'd need that
for a Steam
I think the easiest / most useful solution is adding the libraries to
`commonTargetPkgs` in `pkgs/games/steam/chrootenv.nix`. You can do this
locally by cloning `nixpkgs.git`, modify the file, then running `nix-env
-f . -iA steam` inside the `nixpkgs` directory to install steam in your
user-env
Hi,
Until now usually it's been solved by:
1) Adding needed library to multiPkgs in pkgs/games/steam/chrootenv.nix;
2) Submitting a PR with that.
I'm not sure if we want to add something like `extraDependencies`
argument to Steam; it feels better to me to just add those libraries
11 matches
Mail list logo