Implemented HEVC video demuxing and parsing

build/common.gypi

 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # IMPORTANT:
 # Please don't directly include this file if you are building via gyp_chromium,
 # since gyp_chromium is automatically forcing its inclusion.
 {
   # Variables expected to be overriden on the GYP command line (-D) or by
   # ~/.gyp/include.gypi.
@@ skipping 1813 matching lines @@
         'ozone_platform_ozonex%': 1,
         'use_playready%': 0,
         'conditions': [
           ['target_arch=="arm"', {
             'arm_arch%': '',
             'arm_tune%': 'cortex-a9',
             'arm_thumb%': 1,
             'video_hole%': 1,
           }],
         ],
+        # Enable HEVC/H265 demuxing. Actual decoding must be provided by the

[ddorwin, 2015/06/19 21:40:14]

wolenetz and I were talking, and this should probably only be enabled for
devices that support it. IOW, a "chromecast=1" and "enable_hevc=1" would need to
be set in GYP_DEFINES.

[servolk, 2015/06/20 00:05:07]

Note that this define is added inside chromecast=1 conditional section, so yes,
this is only enabled when explicitly setting chromecast=1 in GYP_DEFINES. Re
enable_hevc flag, see my reply.

[ddorwin, 2015/06/20 00:28:20]

The point is that enable_hevc should not be set when compiling for platforms
that we *know* do not support HEVC. For example, v1 hardware. We should discuss
the build config goals offline.

+        # platform.
+        'defines': ['ENABLE_HEVC_DEMUXING'],

[ddorwin, 2015/06/19 21:40:14]

I'm not sure that defining global defines like this is acceptable (just like GYP
variables).

Since all uses of this define are in media/ (except a test), you should be able
to define this in media.gyp. To satisfy the test, you would also define it
(again) in content_tests.gypi using the same logic.

This is the "right" way to do things and works in this case (unlike things like
USE_PROPRIETARY_CODECS, which are used more widely in other directories).

       }],
       ['chromecast==1 and OS!="android"', {
         'ozone_platform_cast%': 1
       }],
       ['OS=="linux" and target_arch!="mipsel"', {
         'clang%': 1,
       }],  # OS=="mac"
       ['OS=="mac"', {
         'conditions': [
           # All Chrome builds have breakpad symbols, but only process the
@@ skipping 4355 matching lines @@
     # settings in target dicts.  SYMROOT is a special case, because many other
     # Xcode variables depend on it, including variables such as
     # PROJECT_DERIVED_FILE_DIR.  When a source group corresponding to something
     # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
     # files to appear (when present) in the UI as actual files and not red
     # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
     # and therefore SYMROOT, needs to be set at the project level.
     'SYMROOT': '<(DEPTH)/xcodebuild',
   },
 }