commit | 25eee97ce56ba7ed13bd8377678a9c49a5d0c1bc | [log] [tgz] |
---|---|---|
author | Alexandre Zani <azani@chromium.org> | Wed Jun 22 18:22:29 2016 |
committer | Alexandre Zani <azani@chromium.org> | Wed Jun 22 18:22:29 2016 |
tree | 3f6756c0326d522bfde1bc661a194d56e3a10852 | |
parent | 91726a89e3e967f7db74de99da5fdadf03638567 [diff] |
New go generator shakedown. Fix a number of bugs. Add serialization for interfaces and interface requests. Add the sha1 files for the go generator so it is downloaded by gclient sync. R=vardhan@google.com Review URL: https://codereview.chromium.org/2082173002 . Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 58dc9a37daaf13b8da523562c86d0c21a2fc00d3
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.