There are lots of Mojos in the world. For copies of the public library, that's A-OK. For the core implementation, not so much. This is a metabug to track the reduction of Mojo core implementations down to one (1), the source of Truth, in the chromium tree.

There are multiple stages to this:

  * Ship mojo_core shared library on Chrome OS [bug 822034]
  * Introduce the Mojo introduction C API [ bug 844231 ]
  * Migrate all EDK non-initialization API usage over to new public
    API usage [ bug 844763 ]
  * Convert all non-chromium-tree Mojo consumers to use public API
    instead of EDK, and remove EDK from libchrome. [bug 844764]



 

There are lots of Mojos in the world. For copies of the public library, that's A-OK. For the core implementation, not so much. This is a metabug to track the reduction of Mojo core implementations down to one (1), the source of Truth, in the chromium tree.

There are multiple stages to this:

  * Ship mojo_core shared library on Chrome OS [bug 822034]
  * Introduce the Mojo invitation C API [ bug 844231 ]
  * Migrate all EDK non-initialization API usage over to new public
    API usage [ bug 844763 ]
  * Convert all non-chromium-tree Mojo consumers to use public API
    instead of EDK, and remove EDK from libchrome. [bug 844764]