The “V2” command-line interface to Tectonic is substantially new interface to the Tectonic engine introduced in the 0.4.x release series.
In short, the V2 interface is “cargo-like”, with a variety of subcommands anchored around a Tectonic.toml file defining a document to build. For comparison, the original (“V1”) interface is more “rustc-like”, offering a single primary workflow with lots of options controlling its behavior.
The V2 interface is currently available but not the default. It can be activated as described below.
Because the V2 interface is not the current default, it must be explicitly
activated. There are several ways to do this. One way is to use
-X for the
very first command-line argument to the
tectonic executable, like so:
tectonic -X build
It is anticipated that this form of invocation will be supported indefinitely.
Alternatively, if the Tectonic executable is run under a name containing the
nextonic, the V2 interface will also be enabled. In this case, no
is needed (or allowed, at the moment):
You can use various Unix
argv hacks to achieve this, or you can just rename
or symlink the
tectonic binary to
The plan is to eventually migrate to make the V2 interface into the default. This will be implemented as follows:
- Under the current situation, the V2 interface can be explicitly activated
with the leading
-Xflag. The V1 interface can be explicitly selected by using a leading
-Yflag. The default is V1.
- Once the V2 interface is sufficiently stable, the V1 UI will start
recommending that people adopt it via the
-Xflag. Users that want to keep using the V1 interface will be instructed to explicitly select it with the
- After a sufficient amount of time, the V1 interface will be flagged as deprecated.
- After more time has passed, the default will flip: if neither
-Yis provided, the V2 interface will be assumed rather than V1.
- Eventually, the V1 interface may be entirely removed.