manylinux
SDL
manylinux | SDL | |
---|---|---|
13 | 195 | |
1,355 | 8,263 | |
1.8% | 2.4% | |
8.8 | 10.0 | |
4 days ago | 1 day ago | |
Shell | C | |
MIT License | 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.
manylinux
-
Building a go program with an older glibc
I use manylinux containers as the OS for compilation. It tries to ensure as much cross-os / libc / etc.. as much as possible for precompiled libraries. https://github.com/pypa/manylinux
-
Alpine Linux in the Browser
Just to clarify for anyone who isn't aware, the "compiling issues", at least historically, have been that that Alpine uses musl, and PyPI's manylinux wheels are built against old glibc versions. So stuff like numpy that would trivially and quickly install from whl on glibc distros (like a bare-bones Ubuntu image) trigger compilations and the installation of build-only dependencies on Alpine.
That said, it looks like as of late-2021, at least some projects are offering musllinux wheels as well, per the discussion here: https://github.com/pypa/manylinux/issues/37 (not numpy, though: https://pypi.org/project/numpy/#files)
-
Because cross-compiling binaries for Windows is easier than building natively
It's very hard. Incompatible glibc ABIs make this nigh impossible, there's a reason Steam installs a vcredistributable.dll for pretty much every game on Windows.
Look no further than the hoops you need jump through to distribute a Linux binary on PyPI [1]. Despite tons of engineering effort, and tons of hoop jumping from packagers, getting a non-trivial binary to run across all distros is still considered functionally impossible.
[1]: https://github.com/pypa/manylinux
- manylinux_2_28 image is published
- manylinux_2_28 image is published (including docker environment)
-
CPython, C standards, and IEEE 754
As a user, if you build every python package from source, it's ok. But if you a maintainer of an OSS project and you need to publish binary packages for it, then you will hit the trouble. Binaries built on Ubuntu 20.04 can only support Ubuntu 20.04 and newer. So you'd better to choose an older Linux release to target broader users. Now most python packages choose CentOS 6 or 7. See https://github.com/pypa/manylinux/issues/1012 for more details. They need help!
-
Using Zig as Cross Platform C Toolchain
I recently learned that Clang supports this kind of cross-compiling out of the box. https://mcilloni.ovh/2021/02/09/cxx-cross-clang/
The main difference is that Clang does not ship with headers/libraries for different platforms, as Zig appears to do. You need to give Clang a "sysroot" -- a path that has the headers/libraries for the platform you want to compile for.
If you create a bunch of sysroots for various architectures, you can do some pretty "easy" cross-compiling with just a single compiler binary. Docker can be a nice way of packaging up these sysroots (especially combined with Docker images like manylinux: https://github.com/pypa/manylinux). Gone are the days when you had to build a separate GCC cross-compiler for each platform you want to target.
- “LLVM-Libc” C Standard Library
-
'Python: Please stop screwing over Linux distros'
Now you come and use manylinux to build. (https://github.com/pypa/manylinux) so you are based on the CentOS 7 toolchain (at best if you use manylinux2014) or Debian 9 toolchain (if you use manylinux_2_24).
-
Building Outer Wonders for Linux
I think the generally accepted way to do that would be a container image running a relatively old distribution. This is exactly what python packages do when they need to distribute binary packages on linux [0]. You are supposed to compile the package in a container (or VM) that runs CentOS 7 (or older if you want broader support), although now the baseline is moving gradually to Debian 9.
[0]: https://github.com/pypa/manylinux
SDL
-
12to11 – run Wayland applications on an X server
Wayland works well on the Steam Deck because Valve controls the whole system. Because they have their own Wayland compositor (Gamescope), they're able to implement protocols to work around issues in Wayland without being delayed by the bureaucratic process of getting them approved. Here's an SDL pull request where a graphics developer at Valve discusses how two protocols necessary for good GPU performance haven't been added to Wayland yet so Valve added equivalent protocols to Gamescope as a workaround: https://github.com/libsdl-org/SDL/pull/9345
One thing to note is that the Steam Deck only uses Wayland for its fullscreen gaming mode. When you exit to its desktop mode (meant for running non-Steam software), it switches to X11.
-
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.
What are some alternatives?
auditwheel - Auditing and relabeling cross-distribution Linux wheels.
GLFW - A multi-platform library for OpenGL, OpenGL ES, Vulkan, window and input
musl-cross-make - Simple makefile-based build for musl cross compiler
raylib - A simple and easy-to-use library to enjoy videogames programming
glibc_version_header - Build portable Linux binaries without using an ancient distro
Godot - Godot Engine – Multi-platform 2D and 3D game engine
mxe - MXE (M cross environment)
olcPixelGameEngine - The official distribution of olcPixelGameEngine, a tool used in javidx9's YouTube videos and projects
lhelper - A simple utility to helps compile and install C/C++ libraries on Windows and Linux
DS4Windows - Like those other ds4tools, but sexier
padio - Zero pad numeric filenames
DualSenseSupport - Preliminar DualSense