livery.workshop._run¶
livery.workshop._run ¶
Start a package's executable after a development build of what it needs.
fm run <package>[:<executable>] -- <arguments> names a package and
one of the executables its extensions answer under executables
(livery.workshop.EXECUTABLES). It first builds the package's
dependency closure, dependencies first, each member through the steps
its set adds to the build phase's tree side, in the debug
configuration, and skips each member whose files and dependencies are
unchanged since its last good build in this checkout; the record of
those builds lives under .workshop/.cache/run/. Then it runs the
run phase through the one walk
(livery.workshop._phases.walk_steps): every step the
package's set adds to it, except that of the extensions answering
executables only the owner's steps run. The engine gives the phase
the executable under executable, which a step reads as it reads
any engine key, and the words after -- are the context's
arguments. The verb exits with the code the step that started the
executable recorded.
Functions:
| Name | Description |
|---|---|
run |
Build what a package's executable needs, start it, and exit with its code. |
start |
Run target's executable in the workspace at root; its exit code. |
develop |
Build package's dependency closure in the build phase; the paths built. |
Attributes:
| Name | Type | Description |
|---|---|---|
RECORD |
|
|
DEVELOP_INPUTS |
dict[str, dict[str, object]]
|
|
DEVELOP_INPUTS
module-attribute
¶
DEVELOP_INPUTS: dict[str, dict[str, object]] = {'build': {'isolated': False, 'configuration': 'debug'}}
run ¶
run(target: Annotated[Arg[str], doc('package[:executable]; the package may be left out inside its directory, and the executable when the package has one'), suggest(_targets, strict=False)] = '') -> int
Build what a package's executable needs, start it, and exit with its code.
The build phase's tree side runs over the package's dependency
closure first, skipping what is unchanged since its last good
build; then the run phase starts the executable with the words
after --.
Source code in packages/workshop/src/livery/workshop/_run.py
start ¶
Run target's executable in the workspace at root; its exit code.
cwd decides the package a target that names none means. The development build runs first (livery.workshop._run.develop).
Source code in packages/workshop/src/livery/workshop/_run.py
develop ¶
Build package's dependency closure in the build phase; the paths built.
Dependencies come first, each through the steps its set adds to the
build phase that serve the tree side, in the debug
configuration (livery.workshop._run.DEVELOP_INPUTS), run
through the one walk as the release train runs a package's phase.
A member is built when its files, or the fingerprint of a
dependency, differ from its last good build in this checkout, so a
dependency that changed rebuilds what depends on it; a member whose
set adds no such step is never built. With nothing changed, no
build step runs. A checkout git cannot read is built whole, and
says so.