steam-runtime
SDL
Our great sponsors
steam-runtime | SDL | |
---|---|---|
86 | 194 | |
1,153 | 8,157 | |
1.4% | 4.2% | |
6.6 | 10.0 | |
7 months ago | 3 days ago | |
Shell | C | |
GNU General Public License v3.0 or later | zlib License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
steam-runtime
-
One Game, by One Man, on Six Platforms: The Good, the Bad and the Ugly
> It turns out that unless the game is explicitly marked (by Valve reviewers), Steam Deck will use the Windows build + Proton even if a Linux version is available.
I found this which sounds like it's not the default, but is in fact a result of compatibility testing:
> If your game has gone through Steam Deck compatibility testing and the testers reported that the native Linux version didn't work (because of #579), then it might have been flagged to run the Windows binaries via Proton by default, instead of the native Linux version.
per https://github.com/ValveSoftware/steam-runtime/issues/585
-
Chromebook Plus: more performance and AI capabilities
> Where is it written that steam-run will magically execute most binaries without patching them?
Somewhere in here: https://github.com/ValveSoftware/steam-runtime
:p
But I do get what you're saying. Once Flakes are default, I hope people start a proper push to clear up documentation and streamline the development process. The end-result is amazing, and the perfect OS/packaging system for my needs. The means of getting there... need a lot of work. I'm along for the ride either way.
-
i386 in Ubuntu Won't Die
I think they have something a bit like a container built into Steam: https://github.com/ValveSoftware/steam-runtime
- Gaming on Linux easier on Debian based distros vs Arch based?
-
How do you build games for Steam Linux Runtime?
this is for steamworks API, my understanding is there's a separate SDK for consuming Linux dependencies like glibc. Like Soldier runtime, Sniper runtime, and so on. Am I wrong in thinking these are two separate SDKs? here's the link to the other SDK I'm talking about: https://github.com/ValveSoftware/steam-runtime
-
After 4 years of development, 100% on Linux, I've released my 2D sandbox RPG, Vagabond, in Early Access !
I'm not sure we can distribute a flatpak or an appimage through Steam. They have their own controlled environment called Steam Runtime (https://github.com/ValveSoftware/steam-runtime) in which I should compile to be sure it runs everywhere (very similar to what I am doing). Last time, I look at this, it wasn't very clear and they supported only old versions of GCC. But it seems the documentation improved and now that I succeeded in building a modern version of GCC in my own container, maybe I could do that in theirs.
-
How to install old libraries on OTHER distro's than Debian?
I believe it's usable outside of Steam: https://github.com/ValveSoftware/steam-runtime though the instructions are not particularly clear. There's also a link to the APT repo they use as a reference: https://repo.steampowered.com/steamrt/
- Steam Desktop Client Update, Now with working hardware acceleration on linux!
-
Recommended method to install Steam on Debian?
Looking at the Flatpak version, if you want to use Proton versions 5.13 or newer with Steam in Flatpak, you need to install Flatpak from backports https://github.com/ValveSoftware/steam-runtime/issues/294 . Using Flatpak saves having to install i386 if that matters to you.
-
Wine 8.1
> Game developers would be fine to target a single distro like Ubuntu 22.04.
Valve has its own container-only Linux distribution, called "Soldier Runtime" (https://github.com/ValveSoftware/steam-runtime); especially for games distributed on Steam, it probably makes more sense to target that distribution instead of Ubuntu.
SDL
-
C-Macs – a pure C macOS application
The linked project doesn't use any ObjC files at all. SDL2 has a bunch of Cocoa files[1] so you did use Cocoa even if unknowingly.
[1] https://github.com/libsdl-org/SDL/tree/main/src/video/cocoa
-
Revert "video: Prefer Wayland over X11 (take 2)"
Correct. It's explained here:
https://github.com/libsdl-org/SDL/pull/9345#issuecomment-201...
XWayland has special hooks into the compositors that normal wayland clients don't get.
-
Semantic Patching in C with Coccinelle
Found about this through the release of SDL 3: https://github.com/libsdl-org/SDL/blob/main/build-scripts/SD...
-
reflect-cpp - Now with compile time extraction of field names from structs and enums using C++-20.
https://github.com/libsdl-org/SDL/blob/main/include/SDL3/SDL_events.h
-
BBC Basic returns on multiple platforms, open sourced
If that app ran in a 640x480 mode, memory accesses would be just as fast as the VGA applications 25 years ago, correct?
I think there's a lot more going on than that. Here's SDL's current pixel access code:
https://github.com/libsdl-org/SDL/blob/main/src/video/SDL_su...
-
Games! How they write code for SDL (+ interview with the creator)
We use the code examples throughout the article. The ellipsis characters "...." in the code were added by the author of the article. You can find the source files on the official GitHub of libsdl. In addition, each fragment has a reference to a specific area in the code. By the time this article is published, many errors will have already been fixed thanks to the issues we opened (for example, here and there). However, the links in the examples point exactly to the code you see in this article. Not only do we enjoy teasing developers but we also like making their projects a little bit better!
-
Regarding including external libraries and prefix folders.
FetchContent_Declare(SDL2 GIT_REPOSITORY https://github.com/libsdl-org/SDL.git GIT_TAG release-2.28.3 ) FetchContent_MakeAvailable(SDL2)
- SDL3 Filesystem API RFC
-
Chip8 emulator
It's not that difficult, I recently started learning to use graphics APIs myself. OpenGL is for linux, etc., directx for windows and vulkan for all platforms. I read through a bunch of forums yesterday and decided to go for vulkan (here is a link to the sdk) for my next small projects because it can run on all platforms. I would recommend to watch a basic tutorial series (like this one) for the graphics api itself to get an understanding of whats going on. And on top of that I use SDL2 for eventhandling and ImGui for the graphical user interface. Here is a link to a guide for setting up vulkan on your platform in case you would go for it.
-
Felt Cute, Might git rm --rf
SDL (which will be bumped to SDL3), straight from the authoritative https://github.com/libsdl-org/sdl
What are some alternatives?
flatpak - Linux application sandboxing and distribution framework
GLFW - A multi-platform library for OpenGL, OpenGL ES, Vulkan, window and input
dxvk-native - D3D9/11 but it runs natively on Linux!
raylib - A simple and easy-to-use library to enjoy videogames programming
Proton - Compatibility tool for Steam Play based on Wine and additional components
Godot - Godot Engine – Multi-platform 2D and 3D game engine
flathub - Issue tracker and new submissions
olcPixelGameEngine - The official distribution of olcPixelGameEngine, a tool used in javidx9's YouTube videos and projects
steam-for-linux - Issue tracking for the Steam for Linux beta client
DS4Windows - Like those other ds4tools, but sexier
cmake-init-vcpkg-example - cmake-init generated executable project with vcpkg integration
DualSenseSupport - Preliminar DualSense