Bazel rules for compiling LaTeX sources to PDF using tectonic.

Tectonic is self-contained, fast, and pulls TeX Live packages on demand — no system TeX install required. rules_tectonic wraps the upstream prebuilt binaries as a Bazel toolchain and exposes a single rule, tectonic_pdf, that produces a .pdf from a .tex source.

# MODULE.bazel
bazel_dep(name = "rules_tectonic", version = "0.2.0")

During early development you can pin to a git commit via git_override:

bazel_dep(name = "rules_tectonic", version = "0.2.0")
git_override(
    module_name = "rules_tectonic",
    remote = "https://github.com/jesssullivan/rules_tectonic.git",
    commit = "<sha>",
)

# BUILD.bazel
load("@rules_tectonic//tectonic:defs.bzl", "tectonic_pdf")

tectonic_pdf(
    name = "my_paper",
    src = "paper.tex",
    reruns = 1,
    synctex = True,
    deps = [
        "abstract.tex",
        "intro.tex",
        "sections/methods.tex",
    ],
    data = [
        "figures/plot.pdf",
        "refs.bib",
    ],
)

Then:

bazel build //path/to:my_paper
# -> bazel-bin/path/to/my_paper.pdf

Useful optional attributes:

• bundle: a pinned Tectonic bundle file passed with --bundle.
• only_cached: pass --only-cached for builds that must not fetch resources.
• reruns: pass --reruns; defaults to Tectonic's own behavior.
• synctex: generate SyncTeX data in the synctex output group.
• untrusted: pass --untrusted for untrusted TeX inputs.
• format: pass a Tectonic format name or path; defaults to latex.
• extra_args: append advanced tectonic -X compile arguments.

The rule always writes the PDF as its default output and exposes the compile log through the logs output group:

bazel build //path/to:my_paper --output_groups=logs

• A module extension (tectonic_toolchains_ext in //tectonic:extensions.bzl) creates one external repository per supported host platform: @tectonic_linux_amd64, @tectonic_linux_arm64, @tectonic_darwin_amd64, @tectonic_darwin_arm64.
• Each repo downloads the matching prebuilt tectonic binary from tectonic-typesetting/tectonic GitHub releases.
• A toolchain is registered per platform; Bazel picks the right one based on the exec platform.
• tectonic_pdf is a leaf rule that invokes tectonic -X compile <src> --outdir <tmpdir> and moves the resulting PDF to the declared Bazel output.

# MODULE.bazel
tectonic_toolchains = use_extension("@rules_tectonic//tectonic:extensions.bzl", "tectonic_toolchains_ext")
tectonic_toolchains.from_version(version = "0.16.9")

You will need to populate matching SRI integrity strings in tectonic/private/platforms.bzl's RELEASE_INTEGRITY table — pin requests are welcome.

For a given tectonic version, the SRI integrity strings of the prebuilt archives can be obtained from bazel build //examples:hello itself: with an empty integrity entry, Bazel will fetch the archive and print the actual value. Copy that into RELEASE_INTEGRITY[version][platform] for verified, repeatable builds.

You can also compute them directly:

curl -sL <archive-url> | openssl dgst -sha256 -binary | base64 | sed 's/^/sha256-/'

A flake.nix is provided. With direnv:

direnv allow   # uses nix flake; provides bazelisk, tectonic, buildifier

bazel build //examples:hello
bazel test //examples:hello_outputs_test

buildifier is available from both the Nix dev shell and the Bazel module graph:

bazel run //:buildifier.check
bazel run //:buildifier.fix

The public rule reference is generated with Stardoc and checked in at docs/defs.md:

bazel build //docs:defs_doc
bazel test //docs:defs_doc_test

Release archives are generated with:

scripts/make-release-archive.sh 0.2.0 dist

See docs/RELEASING.md for the maintainer runbook.

This repository includes BCR templates under .bcr/ and a consumer-style bzlmod smoke test under e2e/bzlmod/. Registry publication should happen only after the release archive, BCR metadata, and CI presubmit matrix are verified.

MIT — see LICENSE.