* Remove most of mojo/dart/embedder
* Update roll.py to only import a subset of mojo/dart/embedder
* Add mojo/dart/observatory
* Update mojo_sdk_revision to get fixes to dart_pkg.py
This updates to mojo 4e4d51ce28a and mojo sdk 711a0bcfb141b4 and updates the sky
package's pubspec.yaml dependency to '>=0.1.0 <0.2.0' to be compatible with
the current mojo package. This includes an update to the Mojo Dart generator to
produce real classes for enums and the corresponding updates for users of the
KeyboardType enum in Sky as well as one scoped_ptr->std::unique_ptr in shell
corresponding to a change in the Mojo EDK.
When a new version of the sky and sky_services package are pushed this will fix
domokit/mojo#440.
Oneline diffstat: 489 files changed, 4 insertions(+), 186980
deletions(-)
This deletes all of //gpu (except for one export header) and
various bits of //mojo/{gpu,gles2} that are
not used. SkyShell on Android/iOS/etc bind to the system's GL
driver via //ui/gl. sky_viewer.mojo
binds to the Mojo C entry points.
Updates the //mojo snapshotted code and the mojo SDK to
0a98559b4, which includes several cleanups in the GL headers.
Also adds /sky/packages/sky_services/lib to .gitignore
This updates to mojo commit d259eb58aa59 and limits the roll script to
only pull in the parts of //mojo that are currently being used. More
stuff will be dropped in the future.
This means that //mojo/public is pulled in by gclient using the hash
specified in the DEPS file from the github.com/domokit/mojo_sdk mirror.
Each mojo_sdk commit corresponds to its originating
github.com/domokit/mojo commit and has the origin commit in the
message. Thus to find the mojo_sdk revision to use for a particular
mojo revision, grep through the commit log in the mojo_sdk repo for the
matching "Cr-Mirrored-Commit:" line.
If you need to back your local checkout to earlier than this commit
after running gclient, do 'rm -rf mojo/public && git reset --hard' to
get the locally checked in versions back. Otherwise you'll get subtree
commits in mojo/public/... and have a bad time.
We don't import //tonic, which makes this dependency a gn-time failure.
Fortunately, we don't build this target anyway, so we can just remove this
line.
Instead of using a collection of Python scripts to generate the artifacts we
want to distribute from this repository, we should just use the build system.
This CL adds a top-level |dist| target that creates these artifacts in a "dist"
directory of the build output.
