DescriptionSet more consistent conditionals for the use mash flag
In [1], the mash flag was moved outside a ChromeOS conditional
(and inside an "enable mash services" conditional). However, the
corresponding resource definitions in generated_resources.grd were kept
inside a ChromeOS conditional. This broke non-ChromeOS builds when the
mash services are enabled, as it is the case for example with the Ozone
Linux OS bot [2]. This CL moves the resource definitions outside the
ChromeOS conditional.
BUG=None
[1] https://codereview.chromium.org/2681663004/
[2] https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux
Patch Set 1 #
Total comments: 1
Messages
Total messages: 13 (7 generated)
|