tree 20dcbac7cc63e8aa45749dd938802eb0e93027f7
parent d392c019761ca83c3b5ad5462da0a5e18c906bdd
author Wan-Teh Chang <wtc@google.com> 1567186533 -0700
committer Wan-Teh Chang <wtc@google.com> 1569269803 +0000

Fix backward compatibility for CONFIG_LOWBITDEPTH.

1. If CONFIG_LOWBITDEPTH is defined, emit a warning message to suggest
using FORCE_HIGHBITDEPTH_DECODING instead. In addition, if
CONFIG_LOWBITDEPTH is defined as 0, set FORCE_HIGHBITDEPTH_DECODING to
1. (If CONFIG_LOWBITDEPTH is defined as 1, we don't need to set
FORCE_HIGHBITDEPTH_DECODING to 0 because that is the default.)

2. Add FORCE as the final argument to the set() command enabling
FORCE_HIGHBITDEPTH_DECODING. Tom Finegan suggested this change.

Tested:
  cmake ../aom
  cmake ../aom -DFORCE_HIGHBITDEPTH_DECODING=0
  cmake ../aom -DFORCE_HIGHBITDEPTH_DECODING=1
  cmake ../aom -DCONFIG_LOWBITDEPTH=0
  cmake ../aom -DCONFIG_LOWBITDEPTH=1

Then inspect the value of FORCE_HIGHBITDEPTH_DECODING in the files
generated by cmake. The "cmake ../aom -DCONFIG_LOWBITDEPTH=0" and
"cmake ../aom -DCONFIG_LOWBITDEPTH=1" commands should cause cmake to
emit the warning message:
  CONFIG_LOWBITDEPTH has been removed.  Use -DFORCE_HIGHBITDEPTH_DECODING=1
  instead of -DCONFIG_LOWBITDEPTH=0 and -DFORCE_HIGHBITDEPTH_DECODING=0
  instead of -DCONFIG_LOWBITDEPTH=1.
and set FORCE_HIGHBITDEPTH_DECODING to the opposite value (0 <=> 1).

BUG=aomedia:2474

Change-Id: I027aeafbb8a23837dcc7f7718f5705354f616393