There isn't really an upstream package name since this header file is
normally just part of ladspa-sdk.
ladspa-header seems like a more fitting name for this package.
Could also be ladspa-sdk-header, but there are also probably other
headers than ladspa.h in ladspa-sdk.
The multiple-outputs hook doesn't know to handle pkg-config files in
subdirectories like these. Fixing this resolves a reference cycle
that caused building under pkgsStatic to fail.
This commit was created by a combination of scripts and tools:
- an ast-grep script to prefix things in meta with `lib.`,
- a modified nixf-diagnose / nixf combination to remove unused `with
lib;`, and
- regular nixfmt.
Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
It was already bumped to _13 for -bad in:
https://github.com/NixOS/nixpkgs/pull/398009
It's preferable to have the same SDK version across all subpackages, to
avoid potential problems or missing features.
Enabled enableCocoa for -base for x86_64; the new darwin SDK pattern
seems to have fixed the build issue we had before.
Also, cleaned up old darwin sdk stubs for frameworks. These are of no
effect since 24.11 and can be safely removed.
This fails to build, see: https://hydra.nixos.org/build/294125614/log
Setting nvmm support does end up building the required gstcuda module.
However, doing so requires closed-source proprietary
development libraries not yet present in nixpkgs.
This only affects linux on non-x86 processors.
Other platforms are zero rebuilds.
Format all Nix files using the officially approved formatter,
making the CI check introduced in the previous commit succeed:
nix-build ci -A fmt.check
This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153)
of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166).
This commit will lead to merge conflicts for a number of PRs,
up to an estimated ~1100 (~33%) among the PRs with activity in the past 2
months, but that should be lower than what it would be without the previous
[partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537).
Merge conflicts caused by this commit can now automatically be resolved while rebasing using the
[auto-rebase script](8616af08d9/maintainers/scripts/auto-rebase).
If you run into any problems regarding any of this, please reach out to the
[formatting team](https://nixos.org/community/teams/formatting/) by
pinging @NixOS/nix-formatting.
vdpau is a mostly-unsupported hardware acceleration library.
Support for vdpau integration was removed upstream
in 4ff14c0e746eb26874a696b3b71543387fbefa3b [1],
which took effect in 1.17.1 released June 2020 [2].
[1] 4ff14c0e74
[2] https://github.com/GStreamer/gst-plugins-bad/releases/tag/1.17.1
libGLU is an unmaintained GL library.
glu was removed upstream in 6bd1150ca889c17342520b3bbd8e729fb843a1a5 [1],
which took effect in version 1.5.1 released June 2015 [2].
Later, in 769a21d0bb310906b880c07da0e1e2376e11c187 [3],
upstream removed the entirety of direct OpenGL integration.
This change took effect in 1.13.1, released February 2018 [4].
libGLU nix package supplies a couple shared objects,
a package config file, and a single C header.
None of these are used anymore: code search on the package
config comes back empty, and `nix why-depends` confirms
the shared objects are not being linked against.
libGLU is a dependency in many packages, but really should be phased out.
[1] 6bd1150ca8
[2] https://github.com/GStreamer/gst-plugins-bad/releases/tag/1.5.1
[3] 769a21d0bb
[4] https://github.com/GStreamer/gst-plugins-bad/releases/tag/1.13.1
`glib_debug` option (`gobject-cast-checks` prior to 1.26) defaults to `auto`, which would result in the cast checks being disabled on stable versions, if we did not use `-Dauto_features=enabled`. Let’s disable the option as it is meant to be on stable releases: https://gitlab.gnome.org/GNOME/glib/-/blob/main/docs/macros.md#g_enable_debug
Also remove option disabling `glib_asserts`. It was introduced in 800ceaf1bd to remove references to `dev` output caused by `__FILE__` used in assertions but they no longer seem to appear. While the option supported the `auto` means disabled on stable versions feature, the option was actually enabled by default, so the comment was incorrect.
