dev module executables
List each executable this repository's build produces, with the coordinate its build registers under and the build its catalogs hold of this source
- Command version
0.0.0- Command configuration
dev-tool:dev.module.executables@0.0.0
Arguments
It takes none of its own.
It also takes the global arguments.
Output
It answers with a executables.builtExecutables.
Types
executables.builtExecutables
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
executables | list[executables.builtExecutable] | No | [] | Every executable a build of this repository produces when it is run unnarrowed: each kind: executable module, in the order the manifest declares them. A module prebuiltExecutables declares is not among them, since somebody else's build produces it. Empty for a manifest that declares no executable, or states no namespace, since its builds have no coordinate to register under. |
executables.builtExecutable
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
module | string | Yes | The manifest module the executable is built from | |
executable | string | Yes | The name the built executable has, and so the name it is run by once installed: the name the application's definition states, and the module's name where it states none | |
coordinate | string | Yes | The coordinate its build registers under: the manifest namespace, the module name with the platform of the machine asked on it, and the manifest version | |
platform | string | Yes | The platform an executable built on this machine runs on, as <os>-<cpu>: an executable is one platform's, so the answer is this machine's | |
audience | moduleAudience | Yes | Who the module is released to, as its manifest states it and internal where it states none. An application is public or internal: one stating hidden, a library's audience, is reported as it is written and refused by dependency validation | |
stored | string | No | The build of the checkout's source as it stands, built by the adapter the repository resolves now: the one file a store keeps for it -- the executable, or the archive of the directory it sits in -- as an absolute path in the catalog that answered, the repository's own or one it defers to. Absent where no catalog holds one, which is what build would then make | |
publicCoordinate | string | No | The coordinate the client's build of the application registers under, <namespace>:<module>-public-<os>-<cpu>@<version>: the build build --public makes, with the application's internal commands left out. Absent where there is no such build -- an application declared internal has no client, and a public one declaring nothing internal has one build, which is the client's as it stands | |
publicStored | string | No | The client's build of the checkout's source as it stands, as stored answers the whole one. Absent where there is no client's build, or no catalog holds one, which is what build --public would then make |