From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Chromium system ffmpeg
Date: Sat, 19 Jan 2013 11:10:22 -0800 [thread overview]
Message-ID: <50FAEF9E.2070205@gentoo.org> (raw)
In-Reply-To: <20130115095506.6e033640@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On 1/15/13 4:55 AM, Alexis Ballier wrote:
> On Mon, 14 Jan 2013 20:34:42 -0800
> ""Paweł Hajdan, Jr."" <phajdan.jr@gentoo.org> wrote:
>> I'm trying to make Chromium be more compatible with more versions of
>> ffmpeg:
>> <https://groups.google.com/a/chromium.org/d/topic/chromium-dev/fm5Oe_AC3Sc/discussion>
>> (although not stated there, that includes libav).
>
> I've done quite a lot of work for various packages among the past years
> on that side, so if you have specific questions, feel free to ask.
Oh, one more thing: is there an easy way to check whether e.g.
CODEC_ID_OPUS is defined? I just realized it's not a pre-processor
symbol but an enum value so #ifdef wouldn't work.
I could always check the version #defines, but it requires checking
version control to see when it was introduced. It would be great to just
have a way to more simply exclude code that requires CODEC_ID_OPUS.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2013-01-19 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 4:34 [gentoo-dev] Chromium system ffmpeg "Paweł Hajdan, Jr."
2013-01-15 12:55 ` Alexis Ballier
2013-01-16 5:10 ` "Paweł Hajdan, Jr."
2013-01-16 11:54 ` Alexis Ballier
2013-01-16 12:59 ` Rich Freeman
2013-01-16 16:40 ` Alec Warner
2013-01-16 16:48 ` "Paweł Hajdan, Jr."
2013-01-16 13:38 ` Luca Barbato
2013-01-19 19:10 ` "Paweł Hajdan, Jr." [this message]
2013-01-20 9:46 ` Luca Barbato
2013-01-20 18:08 ` "Paweł Hajdan, Jr."
2013-01-21 10:48 ` Alexis Ballier
2013-01-16 13:20 ` Luca Barbato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FAEF9E.2070205@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox