
Make changes to build files to allow packaging chromevox from chromecast builds. Need to split out chromevox and common deps from deps that will only build for chromeos. Also add the ability to specify a manifest file using the FileUtil::LoadExtension method instead of assuming 'manifest.json' hard coded constant. Bug: None Test: Test case, Local chromecast build Change-Id: Id4e5ac0cbb80241536a2e7e3cf48a71dd5f1124a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112573 Reviewed-by: Mike Pinkerton <pinkerton@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Commit-Queue: Randy Rossi <rmrossi@chromium.org> Cr-Commit-Position: refs/heads/master@{#754093}
Cast base
cast_features
This file contains tools for checking the feature state of all of the features which affect Cast products. Cast features build upon the Chrome feature system. Some aspects of Cast require the feature system to work differently, however, so some additional logic has been layered on top. Details are available in comments of the header file. The basics are:
- If you are adding a new feature, add it to
cast_features.cc
so it lives alongside existing features - Add your new feature to the list of
kFeatures
incast_features.cc
const base::Feature kMyFeature{"my_feature", base::FEATURE_DISABLED_BY_DEFAULT};
const base::Feature* kFeatures[] = {
// ..other features
&kMyFeature
}