Move AssistantProxy to a separate build target
This forces us to remove all dependencies on //chromeos/services/assistant, which in turn will allow us to move the implementation to a different mojom service. I ended up choosing a pretty simple cut where I introduce a new |cros_libassistant| target that contains the interfaces that are currently used both by |AssistantProxy| and the Assistant service. Things in this target will eventually have to move over to the new mojom service. Bug: b/171748795 Test: compiled & deployed Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Change-Id: Idb58d45c59b97f3d906fa7e2e148198ec25813a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2518213Reviewed-by:Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Jeroen Dhollander <jeroendh@chromium.org> Cr-Commit-Position: refs/heads/master@{#825095}
Showing
Please register or sign in to comment