[v2] SteamOS Support

corytrese · November 4, 2015, 4:11pm

Wanted to post today a bit about what is required to support SteamOS on Steam.

To successfully ship games to SteamOS you need to do two things. First, build against the SteamRT and second statically link GLFW2. GLFW is not supported by SteamOS, so you cannot depend on it being on a Linux machine.

Setting up Steam Runtime
Install GIT, schroot
apt-get install git
apt-get install schroot

Download SteamRT
git clone https://github.com/ValveSoftware/steam-runtime.git

Build Runtime
cd steam-runtime
./build-runtime.py
cd …

Create the CHROOT
./steam-runtime/setup_chroot.sh --output-dir $PWD --i386

Change Directory into the chroot
schroot -c steamrt_scout_i386 --directory /

NOTES
http://getmoai.com/forums/steam-linux-runtime-build-notes-t3170/
https://gitfundibulum.github.io/2015/09/29/linux-gamedev-tldr/

http://jorgen.tjer.no/post/2014/05/26/self-contained-game-distribution-on-linux/

github.com

jorgenpt/steam-runtime-helpers/blob/master/extract_runtime.sh

#!/bin/bash -e
# Copyright (C) 2014 Jørgen P. Tjernø <jorgenpt@gmail.com>
# This script is licensed under the zlib license, which can be found in
# the LICENSE file.

# Helper script for extracting the steam-runtime that:
#  - Strips unused parts of the runtime (documentation)
#  - Allows you to extract a single architecture
#  - Extracts it to a named directory rather than one that contains the
#    runtime release date.
#
# Usage:
#  $ ./extract_runtime.sh <path to steam-runtime-release_latest.tar.xz> <amd|i386|all> <output directory>

function fatal() { echo "$@" >&2; exit 1; }

if [ $# -lt 3 ]; then
    fatal "Usage: $0 <steam-runtime path> <amd64|i386|all> <output directory>" >&2
fi

This file has been truncated. show original

http://jorgen.tjer.no/post/2014/05/26/self-contained-game-distribution-on-linux/

dogwalker · July 10, 2016, 4:39am

coreytrese, my game has just been greenlit, so I’m heading down this path now, reading the Steam SDK. I’m not familiar with GLFW2. Is that only for Linux builds, or is this something I need to do for my Windows game as well? I’ve built my game with cocos2d-x version 3.10.

Well, dang. The game runs fine on my development machine, but if I copy the folder over to another machine, it simply crashes with a useless message. I’m sure I’ll get this, though. Meanwhile, if there is any documentation on getting the cocos2d-x win32 build to a deployable state, please let me know. Thanks.

dogwalker · July 10, 2016, 10:33pm

I have it working!

corytrese · October 9, 2016, 6:42pm

Did you end up using SteamScoutRT?

dogwalker · October 15, 2016, 4:28am

I haven’t yet, no. I’ve been having to work a lot of overtime with my real job and had to put my project off. My Windows version runs fine on Steam without linking to the Steam SDK (although I’d still like to link to it someday).

However, the Mac version is another story. I run it with cocos2dx version 3-13, which fixes all the screen problems, but my contact at Steam tells me I should link with the SDK so I can add copy protection for the Mac (different approach than the Windows version). So I’ll look at that when I get a break from life.

thanks,
Dogwalker