As we switch mechanisms, it might be a good time to separate support for proprietary codecs from some of the containers that contain them (both currently controlled by USE_PROPRIETARY_CODECS). For example, issue 327115 .
Most buildflags are simple mapping from gn args. However, mojo media does use something fancy, e.g. define macros based on the elements of a list:
https://cs.chromium.org/chromium/src/media/mojo/services/BUILD.gn?rcl=0&l=10
I don't see existing examples how to do this.
brettw: Before I dive in and try do you have any idea on how to do this? Or are there any examples to follow? Thanks!
The build flags just need to end up with a list in the buildflag_header target. So any way you can generate that list will work, including something similar to the way you used to do it.
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by xhw...@chromium.org
, Mar 22 2016