Change the canonical way to include the C bindings headers to <mojo/bindings/*.h>.

- 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).

Review URL: .

Cr-Mirrored-Commit: 26ac597676e474ed12f6a9ffa1f725d92338f7ee
31 files changed
tree: 5bb1a2d48cdeb06a458504ad686f162af7fcca4a
  1. build/
  2. c/
  3. cpp/
  4. dart/
  5. go/
  6. interfaces/
  7. java/
  8. js/
  9. platform/
  10. python/
  11. rust/
  12. third_party/
  13. tools/
  14. .gitignore
  17. mojo.gni
  18. mojo_application.gni
  19. mojo_sdk.gni

Mojo Public API

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.