| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| sdl.m4-Call-PKG_CONFIG-rather-than-hard-coding-pkg-config.patch | sdl.m4: Call $PKG_CONFIG rather than hard-coding pkg-config When cross-compiling, pkg.m4 will set the PKG_CONFIG variable to a suitable pkg-config executable, which might be a host-architecture-prefixed name like aarch64-linux-gnu-pkg-config. This ensures that we will use a suitable search path that is suitable for the host architecture (the machine we are compiling for) rather than the build architecture (the machine we are compiling on) to find dependency libraries like SDL. When using pkg-config as a substitute for sdl2-config, we will similarly need to use the host-architecture-prefixed pkg-config. Setting the PKG_CONFIG environment variable is also the canonical way to request that a different pkg-config implementation be used, if that becomes necessary for some reason. |
Simon McVittie <smcv@debian.org> | no | debian | 2024-01-01 | |
| debian/sdl-config-Remove-libdir-for-multiarch-co-installability.patch | sdl-config: Remove ${libdir} for multiarch co-installability This makes the -dev package multiarch co-installable, allowing compilation of SDL programs for more than one architecture on the same system. This is not an upstreamable change, since it relies on a Debian-specific assumption (that we are installing the library into a directory on the linker's default search path). |
Simon McVittie <smcv@debian.org> | not-needed | 2022-03-02 |