MetaData.h uses multi-char literals. This is kind of gross but probably safe
and hard to change, so this patch allows it while disallowing all other
compiler warnings. (This approach is already used in dom/media/moz.build.)
(An aside: I originally tried using |#pragma GCC ignoring -Wmultichar| to
temporarily disable the warnings in MetaData.h. But that works in gcc but not
in g++ because of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431!)
--HG--
extra : rebase_source : 15ab8d3d6fe4d102b54e270ac7a6ff06af4cbe42
The patch removes 455 occurrences of FAIL_ON_WARNINGS from moz.build files, and
adds 78 instances of ALLOW_COMPILER_WARNINGS. About half of those 78 are in
code we control and which should be removable with a little effort.
--HG--
extra : rebase_source : 82e3387abfbd5f1471e953961d301d3d97ed2973
The HTC version of OMXCodec has extra fields in its ReadOptions class over the
AOSP version. We added padding in bug 932820, but it was apparently not enough.
This patch simply adds more padding to our version of the class.
Samsung's OMX IL doesn't like being instantiated more than once, often leading
to crashes. This patch changes the OMX plugin so that we statically instantiate
one OMXClient to be shared between decoder instances.
Qualcomm's OMXCodec implementation interprets the kClientNeedsFramebuffer flag
to mean that we only want a thumbnail. Thus, it returns only one frame and then
returns EOS.
This patch adds a Qualcomm-specific hack to not pass their decoder this flag.
Qualcomm's OMXCodec implementation interprets the kClientNeedsFramebuffer flag
to mean that we only want a thumbnail. Thus, it returns only one frame and then
returns EOS.
This patch adds a Qualcomm-specific hack to not pass their decoder this flag.
On some devices, HTC has extended android::OMXCodec with their own HTCOMXCodec
which contains some extension that change the ABI.
This patch merely adds padding to MediaSource::ReadOptions, as HTCOMXCodec::read
modifies an HTC-specific field in ReadOptions which doesn't exist in AOSP.
* Added some android::Vector, android::VectorImpl method definitions to link
against.
* Updated android::Vector and android::VectorImpl headers to 4.4 as using
headers from 4.1 crashed 4.4 devices but not vice versa.
Many of the moved variables are likely not needed. moz.build should one
day validate the sandbox's output and error if "useless" variables are
present.
--HG--
extra : rebase_source : 3abdea056c18d00ede8c15b37db60532eca58630
