vmake - Advance and build the newly created version within a Vesta checkout session
vmake [arguments to vesta(1)]
In the most common usage, vmake is invoked from a checkout session's working directory, or from the root directory of a checked-in version or session version, and no arguments are needed.
The vmake command is a small shell script that conveniently builds the next version in a Vesta checkout session, or rebuilds the latest version if nothing has changed.
In more detail, vmake does the following:
- Invoke vadvance(1) to delete junk files and create a new version within the current checkout session if anything in the tree rooted at the working directory has changed.
- Invoke the Vesta evaluator vesta(1) to evaluate the default model in the latest version within the checkout session.
If vmake's current directory is not a Vesta working directory (or a subdirectory thereof), the initial steps are omitted and the evaluator is simply run in the current directory.
All flags and other arguments are passed through to the Vesta evaluator.
- $VESTAFLAGS
- The value of this variable, if any, is placed on the Vesta interpreter's command line just before the arguments copied from vmake's command line.
The following values are obtained from the [UserInterface] section of the Vesta configuration file (vesta.cfg).
- Interpreter
- The filename of the Vesta interpreter to invoke.
- vestaflags
- Default value for $VESTAFLAGS. Empty if not set.
vmake doesn't really do much. Perhaps vupdate(1) should (optionally) be invoked too.
Perhaps the name "vmake" should have been reserved for some kind of Makefile-compatibility tool, but as yet there is none.
This page was generated automatically by mtex software.