Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds:
see chrome/common/features.gni
enable_package_mash_services = is_chromeos
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and then make
::MashMain codepath accessible (triggered by --mus and --mash
command line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus`
linux/ozone builds continue to launch on off-trunk [2]. For
ChromeOS matters, it does not change anything.
[1] https://codereview.chromium.org/2755813002/diff/300001/chrome/app/chrome_main.cc
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None

Description was changed from
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in accordance
to its gn variable counterpart, $enable_package_mash_services.
Until [1], it was possible to set enable_package_mash_services=true
for non chromeos builds (e.g. ozone/linux os) and the MashMain codepath
was accessible (triggered by --mus and --mash command line parameters).
This CL relaxes the chromeos enforcement so that chrome --mus on
off-trunk [2] linux/ozone builds continue to launch.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========
to
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds.
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and the MashMain
codepath was accessible (triggered by --mus and --mash command
line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus` on
off-trunk [2] linux/ozone builds continue to launch.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========

Description was changed from
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds.
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and the MashMain
codepath was accessible (triggered by --mus and --mash command
line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus` on
off-trunk [2] linux/ozone builds continue to launch.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========
to
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds:
see chrome/common/features.gni
enable_package_mash_services = is_chromeos
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and then make
::MashMain codepath accessible (triggered by --mus and --mash
command line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus` linux/ozone
builds continue to launch on off-trunk [2]. For ChromeOS
matters, it does not change anything.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========

tonikitoo

Description was changed from ========== Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos builds ...

Description was changed from
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds:
see chrome/common/features.gni
enable_package_mash_services = is_chromeos
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and then make
::MashMain codepath accessible (triggered by --mus and --mash
command line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus` linux/ozone
builds continue to launch on off-trunk [2]. For ChromeOS
matters, it does not change anything.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========
to
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds:
see chrome/common/features.gni
enable_package_mash_services = is_chromeos
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and then make
::MashMain codepath accessible (triggered by --mus and --mash
command line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus`
linux/ozone builds continue to launch on off-trunk [2]. For
ChromeOS matters, it does not change anything.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========

tonikitoo

Description was changed from ========== Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos builds ...

Description was changed from
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds:
see chrome/common/features.gni
enable_package_mash_services = is_chromeos
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and then make
::MashMain codepath accessible (triggered by --mus and --mash
command line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus`
linux/ozone builds continue to launch on off-trunk [2]. For
ChromeOS matters, it does not change anything.
[1] https://codereview.chromium.org/2755813002
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========
to
==========
Allow 'enable_package_mash_services' GN flag to be functional for non-chromeos
builds
The ENABLE_PACKAGE_MASH_SERVICES compile flag is enabled in
accordance to its gn variable counterpart, $enable_package_mash_services,
which by default is enabled for ChromeOS builds:
see chrome/common/features.gni
enable_package_mash_services = is_chromeos
Until [1], it was possible to set enable_package_mash_services=true
for non-ChromeOS builds (e.g. ozone/linux os) and then make
::MashMain codepath accessible (triggered by --mus and --mash
command line parameters).
This CL relaxes the ChromeOS enforcement so that `chrome --mus`
linux/ozone builds continue to launch on off-trunk [2]. For
ChromeOS matters, it does not change anything.
[1]
https://codereview.chromium.org/2755813002/diff/300001/chrome/app/chrome_main.cc
[2] https://github.com/Igalia/chromium/tree/ozone-wayland-devR=ben@chromium.org
BUG=None
==========