diff options
| author | Rhys-T <108157737+Rhys-T@users.noreply.github.com> | 2025-07-01 20:09:28 -0400 |
|---|---|---|
| committer | Rhys-T <108157737+Rhys-T@users.noreply.github.com> | 2025-07-01 20:09:28 -0400 |
| commit | 08e498ee47a63b2d3c23a592dcd1530685f18594 (patch) | |
| tree | 6a7b65acd9a91f4e7bcf9bc1d18317d3c359d73a /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 376a91ea0506c2963296a955cc6c401274cdc978 (diff) | |
mame: use absolute path to bgfx data directory
Currently if you try to use the `bgfx` renderer, MAME outputs an error:
```
Unable to find the BGFX path bgfx, please install it or fix the bgfx_path setting to use the BGFX renderer.
Initializing video module bgfx failed, falling back to opengl
```
because it's looking for the `bgfx` directory inside the working
directory. To fix this, you have to explicitly set `bgfx_path` to
`/nix/store/whatever1234hash567890-mame-0.277/opt/mame/bgfx`.
This commit changes the default `bgfx_path` to be an absolute path to
the right place, similarly to what's already being done for `artpath`,
`ctrlrpath`, etc. However, unlike those options, `bgfx_path` can only
take a single directory - so this is technically a breaking change if
you actually _wanted_ MAME to use `./bgfx`.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions