Enabling Mus in content shell

[santosh...@gmail.com]

Good morning devs,

I am doing work for porting wayland to chromium embedded work. but it seems that
content layer(content_shell) ozone build is broken, it warns to use the MUS codepath for content_shell for ozone build.

So I was trying to implement mus path in cef/content layer. Related with this I have few questions:

How tightly coupled is current MUS code with chrome codebase. I mean is it feasible to port mus services on content layer? I mean by implementing the delegates function and musclient initialisation.

I see some initial error regarding catalog manifest not providing ui manifest. so
in content shell it fails to resolve service name and closes the connection with ui services. Is there any requirement to provide manifest for each services, where can I get that as sample. any hint to fix this problem?

Is there any good docs/guideline available for mus initialisation

Thanks in advance.

Regards
Santosh