Overload YCbCrImageDataSerializer.InitializeBufferInfo to take explicit plane
offsets. Make SharedPlanarYCbCrImage::SetDataNoCopy set the offsets based on the
Y, Cb and Cr plane pointers passed by the caller.
There are two parts to this. The first is to add AndroidManifest.xml
as a dependency to the "no dependencies" ap_ built during packaging.
The aapt call requires it. So "no dependencies" is more accurately
"no *resource* dependencies".
The second is to avoid including the Android res/ directory in the
language repack step. What happens is that the l10n.py script sees
the Android res/ files left in the dist/ directory after unpacking and
expects to find them in the objdir. They're not there, so the script
fails. To avoid this, we delete them after unpacking. See the
comments in packager.mk describing this process.
--HG--
extra : rebase_source : 35c3c125dddcd575c1a5e8ad58f9aa13ff2db4c3
========
https://hg.mozilla.org/integration/gaia-central/rev/de7d1d59e942
Author: Anthony Ricaud <anthony@ricaud.me>
Desc: Revert "Revert "Merge pull request #14667 from mcav/utf7""
This reverts commit 7852023abb572c522a07af558e7c19f557cc4866.
That was a wrong revert, it didn't fix the failing tests.
========
https://hg.mozilla.org/integration/gaia-central/rev/5449cb5b262e
Author: Anthony Ricaud <anthony@ricaud.me>
Desc: Revert "Merge pull request #14667 from mcav/utf7"
This reverts commit cfa88581f0bdaa3d4b7a3773ae87edc55260a2ab, reversing
changes made to b44a75862ebcb651381eabc9c3a3b203d76d63bf.
This is breaking 6 integration tests
Previously, the set of WebIDL example interfaces to build was hardcoded
in the mozwebidlcodegen Python package. Unfortunately, the example
interfaces in that set were dependent on test-only bindings files,
resulting in build failures when tests were disabled (because those
test-only bindings were defined in a test directory).
In this patch, we now declare example interfaces in moz.build files
so the set of example interfaces lives next to the set of defined
bindings files. The example interfaces are defined in a test moz.build
file - in the same file declaring the bindings files that contain the
interfaces - so the example interfaces only get picked up if the
corresponding bindings are defined.
We could probably switch WebIDL moz.build variables to use lists with
flags. That would be good followup fodder. For now, let's fix the build.
--HG--
extra : rebase_source : 00070a6d560625bc84ab9b10d6848ea037f8f5ed
extra : amend_source : 0890ecef444ba58533fcfaa333773d78deafd7f3
