|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | - | - |
| c/ | | 03-May-2024 | - | 3,205 | 1,881 |
| cpp/ | | 03-May-2024 | - | 15,235 | 10,526 |
| gles2/ | | 03-May-2024 | - | 36 | 30 |
| go/mojo/system/ | | 03-May-2024 | - | 10 | 4 |
| interfaces/ | | 03-May-2024 | - | 1,930 | 1,539 |
| java/ | | 03-May-2024 | - | 4,957 | 2,299 |
| js/bindings/ | | 03-May-2024 | - | 3,028 | 2,183 |
| platform/native/ | | 03-May-2024 | - | 748 | 509 |
| python/ | | 03-May-2024 | - | 2,507 | 1,953 |
| tests/ | | 03-May-2024 | - | 111 | 71 |
| tools/bindings/ | | 03-May-2024 | - | 8,243 | 6,519 |
| BUILD.gn | D | 03-May-2024 | 1.1 KiB | 48 | 42 |
| DEPS | D | 03-May-2024 | 72 | 7 | 6 |
| README.md | D | 03-May-2024 | 1.4 KiB | 44 | 31 |
README.md
1Mojo Public API
2===============
3
4The Mojo Public API is a binary stable API to the Mojo system.
5
6It consists of support for a number of programming languages (with a directory
7for each support language), some "build" tools and build-time requirements, and
8interface definitions for Mojo services (specified using an IDL).
9
10Note that there are various subdirectories named tests/. These contain tests of
11the code in the enclosing directory, and are not meant for use by Mojo
12applications.
13
14C/CPP/JS
15--------
16
17The c/, cpp/, js/ subdirectories define the API for C, C++, and JavaScript,
18respectively.
19
20The basic principle for these directories is that they consist of the source
21files that one needs at build/deployment/run time (as appropriate for the
22language), organized in a natural way for the particular language.
23
24Interfaces
25----------
26
27The interfaces/ subdirectory contains Mojo IDL (a.k.a. .mojom) descriptions of
28standard Mojo services.
29
30Platform
31--------
32
33The platform/ subdirectory contains any build-time requirements (e.g., static
34libraries) that may be needed to produce a Mojo application for certain
35platforms, such as a native shared library or as a NaCl binary.
36
37Tools
38-----
39
40The tools/ subdirectory contains tools that are useful/necessary at
41build/deployment time. These tools may be needed (as a practical necessity) to
42use the API in any given language, e.g., to generate bindings from Mojo IDL
43files.
44