This is a tracking bug.
Change our build rules in src/ash such that they only support builds with target_os="chromeos". ash_unittests and ash_shell_with_content will stop compiling on Windows and on non-chromeos Linux. This will simplify our build configs, source code, and tests.
Details: A few years ago we shipped the ash window manager and system UI on Windows to support "Metro-mode" in Windows 8. This never really caught on, so we stopped doing it and the Windows support for ash in src/chrome was removed.
However, ash_unittests and ash_shell_with_content were left on the build bots for Windows. A couple of developers on the mustash team have been using these build targets for developing the mus window server on Windows. They've agreed that maintaining another config is more expensive than the benefit they get from it (thanks, guys!).
beng@ is going to throw together a lightweight mus window manager that can run on Windows. That will allow development of the mus window server and testing of ui and views code.
The ash targets currently compile on non-chromeos Linux, but don't run, and have not done so for months. I will remove support for non-chromeos Linux as well.
I would like to do the following things:
1. Take the ash_unittests target off all the non-chromeos bots
2. Simplify the BUILD.gn files to remove is_chromeos blocks
3. Eliminate unnecessary cross-platform base classes (like I did recently with TrayAudio vs. TrayAudioChromeos)
4. Flatten the directory structure to remove .../chromeos/... directories
5. (Maybe) clean up #if defined(OS_CHROMEOS) code
See blocked-on for individual tasks.
Comment 1 by jamescook@chromium.org
, Nov 18 2016