Bug#1030890: libwebm: Provide additional headers to alllow building aom with the system libwebm

[Vladimir Petko <vladimir.petko@canonical.com>]

Hi,

I do not believe that maintaining either API or ABI compatibility is
the goal of the upstream[1].
Microsoft exposes those headers in their vcpkg packaging[2].
As far as I understood, the official upstream stance is to bundle the
library in /third_party/ folder.
The headers need to be exposed for the dependencies such as aom to be
built, otherwise the library has to be bundled.
If the bundling is ok, and this is what's happening now, I will close
this issue and the related one in aom as invalid.

Best Regards,
 Vladimir

[1] https://groups.google.com/a/webmproject.org/g/webm-discuss/c/7ztiZTH8xBA/m/ahIbZOIiN3gJ
[2] https://github.com/microsoft/vcpkg/commit/b11941140ce64dd4ccefec44fed6a7719ba3aaf5

On Sun, Feb 12, 2023 at 9:49 PM Sebastian Ramacher <sramacher@debian.org> wrote:
>
> Control: tags -1 moreinfo
>
> Hi Vladimir
>
> On 2023-02-09 08:37:06 +1300, Vladimir Petko wrote:
> > Package: libwebm
> > Severity: wishlist
> > Tags: patch
> > User: ubuntu-devel@lists.ubuntu.com
> > Usertags: origin-ubuntu lunar ubuntu-patch
> > X-Debbugs-Cc: vladimir.petko@canonical.com
> >
> > Dear Maintainer,
> >
> > In order to build aom using the system libwebm, aom needs access to
> > /mkvparser/* and
> > /mkvmuxer/* headers.
> >
> > In Ubuntu, the attached patch was applied to achieve the following:
> >
> >    Update CMakeLists.txst so that /mkvparser/* and /mkvmuxer/* headers are
> > provided
> >    in /usr/include/webm/mkvparser and /usr/include/webm/mkvparser
> > respectively
> >
> >   * debian/patches/0004-add-public-headers.patch: Add additional public
> > headers
> >     for aom build
> >
> > Thanks for considering the patch.
>
> Are the symbols from these headers covered by upstream's ABI guarantees?
>
> Cheers
> --
> Sebastian Ramacher