Arch Linux User Repository

@Fresco thank you for the suggestion, i believe upstream is already aware of the issue https://github.com/obsproject/obs-studio/issues/2625

Re: 1: I’m not sure what you mean, ShayBox? The "obs-ndi-4.9.0.tar.gz" file is an archive of the plugin’s sources, not a binary build of the module. This is perfectly as it should be.

Re: 2: Agreed, but until ndi-sdk provides libndi, no reason to make a change here.

Re: 3: Have you considered filing an issue at https://bugs.archlinux.org/ (or maybe it’s an upstream issue?) emileet? Seems like something other OBS plugins would need to compile too, and it is a bit heavy to download the complete OBS source code when what is needed should already be available. However, it is not an issue with this package as-is, but an issue that needs fixing either in the Arch Linux package and/or with upstream.

@ShayBox the reason for the binary sources is to verify the integrity of the source files with makepkg, although unnecessary i find it to be good practice. i'm happy to just checkout releases instead if you prefer but i prefer this way as it's a continuity of how upstream obs-studio is built.

your concern of ndi-sdk is valid in the event ndi-sdk updates so i will make the adjustments when obs-ndi is updated, the original reason for this choice was to consider users who may require the header files from ndi-sdk.

the reason why we're sourcing obs-studio is due to the fact that building the plugin requires the "obs-frontend-api.h" header which isn't provided by the obs-studio package (pacman -Ql obs-studio | grep frontend).

This package should be compiling from tagged sources, not sourcing from tagged binary sources.
It should be depending on libndi not ndi-sdk, one is a shared package group, the other is a single package.
And it should also not be pulling obs-studio, this is a plugin, you don't need to install obs.