dev build

Build project modules and artifacts

Command version
0.0.0
Command configuration
dev-tool:dev.build@0.0.0

Arguments

ArgumentTypeRequiredDefaultDescription
--moduleslist[string]No[]Optional module namesRepeatable
--pathslist[string]No[]Optional explicit pathsRepeatable
--outstringNoOutput executable path, directory and filename together (default: the module's name under bin/ in the repository's build catalog). A packager that builds a directory writes it beside that filename, named without an executable suffix
--rebuild, --no-rebuildbooleanNofalseBuild even where the build catalog already holds an artifact for this source state, and register what comes out over it
--libraries-only, --no-libraries-onlybooleanNofalsePopulate the build catalog with this repository's library modules and build no executable. What a consumer of those libraries needs made, without paying for a packager run it will not use
--public, --no-publicbooleanNofalseBuild the public executable of each application that has one, and nothing else: an application declared audience: public in the manifest that holds a command or a registry declared internal, built with those left out -- their packages, their files and the entries naming them -- rather than hidden. It is written to bin/public/ under the build catalog, under the application's own name, and registered under a coordinate of its own. An internal application has no public build, and a public one with nothing internal has one build, which is the public one as it stands
--recurse, --no-recursebooleanNofalseRun this command in every repository this one pins as a kind: repository module, as that repository's own build in its own checkout, so that repository's own configuration decides what it means, and promote what each populates into this repository's build catalog. Without it a build covers this repository's own modules and stops at every pinned checkout. Every repository is built even when one fails, and each failure names the repository it came from. A run narrowed with --modules or --out crosses into nothing either way
--check-arglist[string]No["--help"]The arguments a built artifact is run with to ask whether it starts; repeatable, and written --check-arg=--help where the value is itself an option. A non-zero exit, a crash or no answer fails the build. An empty list, set under argDefaults, turns the check off, which is the honest setting for a repository whose artifacts cannot be asked anything without doing workRepeatable
--check-timeout-secondsintegerNo60How long the start-up check may take before it counts as a failure. An artifact that waits for input rather than answering would otherwise hang the build rather than fail it

It also takes the global arguments.

Output

It answers with a AdapterOutput.