commit | ff9b6c3da0ba00ed7f6ad83620a0fb546dad8075 | [log] [tgz] |
---|---|---|
author | Zachary Anderson <zra@google.com> | Fri Jul 01 21:24:45 2016 |
committer | Zachary Anderson <zra@google.com> | Fri Jul 01 21:24:45 2016 |
tree | ffff5f0a2bd4d26a0031b66a6b4082e9b09871f2 | |
parent | 5a7918e5b63106c5b8b2cc43bbdd424af8e81885 [diff] |
Dart: Fixes enum array encoding fixes #799 R=johnmccutchan@google.com Review URL: https://codereview.chromium.org/2112313002 . Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 9397aa588d55e96077c3859d4a136e4e6adf57ea
The Mojo Public API is a binary stable API to the Mojo system.
It consists of support for a number of programming languages (with a directory for each support language), some “build” tools and build-time requirements, and interface definitions for Mojo services (specified using an IDL).
Note that there are various subdirectories named tests/. These contain tests of the code in the enclosing directory, and are not meant for use by Mojo applications.
The c/, cpp/, js/ subdirectories define the API for C, C++, and JavaScript, respectively.
The basic principle for these directories is that they consist of the source files that one needs at build/deployment/run time (as appropriate for the language), organized in a natural way for the particular language.
The interfaces/ subdirectory contains Mojo IDL (a.k.a. .mojom) descriptions of standard Mojo services.
The platform/ subdirectory contains any build-time requirements (e.g., static libraries) that may be needed to produce a Mojo application for certain platforms, such as a native shared library or as a NaCl binary.
The tools/ subdirectory contains tools that are useful/necessary at build/deployment time. These tools may be needed (as a practical necessity) to use the API in any given language, e.g., to generate bindings from Mojo IDL files.