
Have chromecast use the same auto-numbered tools/gritsettings/resource_ids.spec as other targets so that collisions do not occur when repacked (as happened on cast_shell_linux bot on https://chromium-review.googlesource.com/c/chromium/src/+/3107487/5). Bug: None Change-Id: I3123733b2618113239eec6ac44f280246b69721c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3115490 Reviewed-by: Sean Topping <seantopping@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/main@{#914787}
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
}