manta-cli 2.0.0-beta.3

Another CLI for ALPS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

//! Generate man pages and shell completions into cargo's `OUT_DIR`.
//!
//! Writing to `OUT_DIR` (per cargo convention) keeps the source tree
//! untouched on every build, which is what `cargo publish`'s verify
//! step requires. The generated files end up at:
//!
//!   target/{profile}/build/manta-cli-{fingerprint}/out/man/*.1
//!   target/{profile}/build/manta-cli-{fingerprint}/out/completions/*
//!
//! `dist` (in `dist-workspace.toml`) glob-includes those paths into
//! release tarballs. The `{fingerprint}` hash varies between builds,
//! so the glob is `target/release/build/manta-cli-*/out/...`.
//!
//! For local inspection:
//!
//!   cargo build -p manta-cli --release
//!   find target/release/build -path '*/manta-cli-*/out/man'
//!
//! There are no committed copies in the source tree.

use clap_complete::{Shell, generate_to};
use clap_mangen::generate_to as generate_man_to;
use std::fs;
use std::io::Error;
use std::path::PathBuf;

#[path = "src/cli/build/mod.rs"]
mod cli;

fn main() -> Result<(), Error> {
  // cargo always sets OUT_DIR for build scripts; the .expect() is
  // safe by contract.
  let out_dir = PathBuf::from(
    std::env::var_os("OUT_DIR").expect("cargo always sets OUT_DIR"),
  );

  // ── Man pages ─────────────────────────────────────────────────────────────
  let man_dir = out_dir.join("man");
  fs::create_dir_all(&man_dir)?;
  generate_man_to(cli::build_cli(), &man_dir)?;

  // ── Shell completions ──────────────────────────────────────────────────────
  let completion_dir = out_dir.join("completions");
  fs::create_dir_all(&completion_dir)?;
  for shell in [Shell::Bash, Shell::Zsh, Shell::Fish, Shell::Elvish] {
    generate_to(
      shell,
      &mut cli::build_cli(),
      env!("CARGO_PKG_NAME"),
      &completion_dir,
    )?;
  }

  Ok(())
}