| commit | c108edf15e6ecd373de1a51bc1acbcabe6039a9b | [log] [tgz] |
|---|---|---|
| author | Viet-Trung Luu <viettrungluu@chromium.org> | Wed Aug 10 20:33:54 2016 |
| committer | Viet-Trung Luu <viettrungluu@chromium.org> | Wed Aug 10 20:33:54 2016 |
| tree | 5fe45d92ac0cddb4c4a5382faf5eef0f1e9cdadf | |
| parent | 4c57ce16133def5acea803ae4e487fabfaa7d027 [diff] |
Move mojo/public/c/environment/tests to mojo/public/c/tests/environment. R=jamesr@chromium.org Review URL: https://codereview.chromium.org/2235993002 . Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 03a3949b7da7f0f56ab05a2aed4bfe147a072cfe
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.