Bug#1094383: libvst3sdk-dev: misses module_linux.cpp

[Andrius Merkys <merkys@debian.org>]

Hi,

On 2025-01-27 18:47, IOhannes m zmölnig (Debian/GNU) wrote:
> I recently had a discussion with an upstream that would like to get
> their package into Debian.
> they mentioned that the libvst3sdk-dev provided by Debian
> > isn't complete as it doesn't ship e.g. module_linux.cpp which is supposed to be built by the host application using the SDK
>
> (the discussion is somewhere on <https://github.com/ossia/score/issues/1476#issuecomment-2456190614>)
>
> i know to little about vst3sdk to validate this, but a quick glance at
> the vst3sdk sources suggests they are correct.
>
> I see that there's a libvst_hosting.a, which might acdtually contain a
> pre-built module_linux.o, but a quick 'strings' test shows that at least
> some symbols do not appear.
>
>
> i do not know what the correct way to proceed is (e.g. ship
> module_linux.cpp, build it into libvst_hosting.a, or dismiss the notion
> of the ossia upstream altogether).
> as such i don't even known what the proper severity of this bug is.
>
> but i thought i'd report it anyhow.

Thanks for reporting this. Last week I attempted un-embedding vst3sdk 
from juce and ran into a similar issue, as juce similarly wants to 
include vst3sdk's .cpp files. I did not attempt to collect the list of 
needed .cpp files.

I think shipping the .cpp files in libvst3sdk-dev would be the most 
convenient right now, as that would minimize the need to patch the 
depending sources. I am as well not enough familiar with vst3sdk to say 
how its upstream intend it to be used, I can only see how it is done in 
practice.

Best,
Andrius