Skip to content

Conversation

@techmccat
Copy link

Closes #179

Fixes VA-11 Hall-A (and probably other GameMaker Studio 1 games) not starting on new installs that don't have the old steam runtime

@strycore
Copy link
Member

Have you tested this?

@strycore
Copy link
Member

By tested, I mean have you run runtime/build.sh

@techmccat
Copy link
Author

As far as I've seen the runtime build process isn't documented, I ran it now in a Ubuntu 18.04 container after installing sudo, lsb-release and adding i386 packages

It seems the new files are in both of the Ubuntu-18.04 directories, pointing LD_LIBRARY_PATH to the i386 one has the game run fine
The x86-64 directory is the only one that gets made into a tarball, but that looks like an issue with the build script

@strycore
Copy link
Member

Our immediate goal is to abandon the 18.04 runtime and switch everything to Pressure Vessel so I'm not sure how useful it is to keep feeding its corpse.

@techmccat
Copy link
Author

Which libraries would go into the pressure vessel containers then?
Because unfortunately I suspect there are going to be a few games needing libssl1.0, since it was included in the original steam linux runtime

@strycore
Copy link
Member

Pressure Vessel is built by Valve so we don't control what goes in it. We can likely add compatibility modes for Steam Runtime V1 and V2.

But ideally, the preferred method would be to add required libs for a game as metadata so we can pull those libs automatically and create a lib32 or lib64 folder in the game folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider including libssl1.0.0 in the Linux runtime

2 participants