commit | c77beb9853c1bb64f18a96f61b370dc3bee99160 | [log] [tgz] |
---|---|---|
author | Viet-Trung Luu <viettrungluu@chromium.org> | Wed Aug 10 20:32:29 2016 |
committer | Viet-Trung Luu <viettrungluu@chromium.org> | Wed Aug 10 20:32:29 2016 |
tree | 5bb1a2d48cdeb06a458504ad686f162af7fcca4a | |
parent | d63eb7daf6fd791b85403ebfb637c3b626da480e [diff] |
Change the canonical way to include the C bindings headers to <mojo/bindings/*.h>. Also: - The .c files go into mojo/public/c/lib/bindings. - The .h files formerly go into mojo/public/c/bindings/internal (they're actually included by public headers, so they can't go under lib). - I haven't moved the tests yet (to be done separately). R=jamesr@chromium.org Review URL: https://codereview.chromium.org/2232833003 . Cr-Mirrored-From: https://github.com/domokit/mojo Cr-Mirrored-Commit: 26ac597676e474ed12f6a9ffa1f725d92338f7ee
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.