commit | 6b5fb1227c742f5ecc077486ebc029f2711c61fa | [log] [tgz] |
---|---|---|
author | Vardhan Mudunuru <vardhan-cr@chromium.org> | Thu Aug 04 20:07:17 2016 |
committer | Vardhan Mudunuru <vardhan-cr@chromium.org> | Thu Aug 04 20:07:17 2016 |
tree | ea113651e1e0c87ff42492d6c013c061ddd06e98 | |
parent | ee5c8d5caa0e9628fd07bf9544551ca23f484b22 [diff] |
C bindings string descriptor: Use field initializers. R=viettrungluu@chromium.org Review URL: https://codereview.chromium.org/2218493002 . Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 969b831b9a6916cd34e41cbaa51e9655d82d9ca2
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.