This is a bit of a special thing and it may well be not solvable.
We (KDE) are building a content snap with all our core libraries. To then build aginst libraries in this content snap we also create a tarball of the stage of the content snap (i.e. a tar containing every libray and header pertaining to the content snap).
To consume this one would have a dummy 'dump' part that uses the tarball as source. This works for the most part. It does however not work for pulseaudio. Specifically usr/lib/x86_64-linux-gnu/libpulse.so.0 needs usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so (note the subdir). Since we have both in the content snap and the associated dev tarball, a consumer should not need to install this, ld however falls flat on the face.
In a build environment libpulse0 would not be a stage-package, as such not installed in the system, and thus ld won't be able to resolve pulsecommon (supposedly because of the subdir).
This is a bit of a special thing and it may well be not solvable.
We (KDE) are building a content snap with all our core libraries. To then build aginst libraries in this content snap we also create a tarball of the stage of the content snap (i.e. a tar containing every libray and header pertaining to the content snap).
To consume this one would have a dummy 'dump' part that uses the tarball as source. This works for the most part. It does however not work for pulseaudio. Specifically usr/lib/ x86_64- linux-gnu/ libpulse. so.0 needs usr/lib/ x86_64- linux-gnu/ pulseaudio/ libpulsecommon- 8.0.so (note the subdir). Since we have both in the content snap and the associated dev tarball, a consumer should not need to install this, ld however falls flat on the face.
In a build environment libpulse0 would not be a stage-package, as such not installed in the system, and thus ld won't be able to resolve pulsecommon (supposedly because of the subdir).