![]() ![]() $ file * | grep ELF | cut -d: -f1 | LD_LIBRARY_PATH=. If individual games or Steam itself is failing to launch when using steam-native you are probably missing libraries. Please note that most of these "missing" libraries are actually already included with Steam, and do not need to be installed globally. ![]() game_executable is likely located somewhere in ~/.steam/root/steamapps/common/. You can find out what libraries it requests by running ldd game_executable. If a game fails to start, a possible reason is that it is missing required libraries. If you figure out a missing library you can use pacman or pkgfile to search for packages that contain the missing library. To correctly debug a program or shared library it is therefore important that these environment variables in your debug environment match the environment you wish to debug. The LD_LIBRARY_PATH and LD_PRELOAD environment variables can alter which shared libraries are loaded, see ld.so(8). To see the shared libraries required by a program or a shared library run the ldd command on it, see ldd(1). You can also use the Steam native runtime without steam-native-runtime by manually installing just the packages you need. This package provides the steam-native script, which launches Steam with the STEAM_RUNTIME=0 environment variable making it ignore its runtime and only use system libraries. The steam-native-runtime package depends on over 130 packages to pose a native replacement of the Steam runtime, some games may however still require additional packages. Warning: Using the Steam native runtime is not recommended as it might break some games due to binary incompatibility and it might miss some libraries present in the Steam runtime. the OpenAL version of the Steam runtime lacks HRTF and surround71 support. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |