CMDLINER-INS...-TOOL-SUPPORT(1)
π CMDLINER-INS...-TOOL-SUPPORT(1)
okay so bestie, welcome to the manual page for cmdliner-install-tool-support β that's the Cmdliner Manual, section 1, and it's genuinely the "do both things at once" icon we all needed π
β¨ NAME β¨
cmdliner-install-tool-support β Install both tool completion and manpages. that's it, that's the whole vibe. two jobs, one command, main character energy fr π
πΈ SYNOPSIS πΈ
cmdliner install tool-support [OPTION]β¦ TOOLEXEC[:NAME]β¦ PREFIX
π¦ DESCRIPTION π¦
so cmdliner install tool-support is literally just install tool-completion and install tool-manpages holding hands π«Ά it installs all the tool support files into a given PREFIX β and it assumes that PREFIX follows the Filesystem Hierarchy Standard. slay.
but listen, if that's not your situation (like, say, in opam as of writing π), use the options --sharedir and/or --mandir to point it where you actually want stuff to go.
and pls, do yourself a favor: use option --dry-run to see which paths would be written before anything actually gets written. it's giving responsible queen behavior π
example time, no cap:
cmdliner install tool-support ./mytool /usr/local
cmdliner install tool-support --update-opam-install=mypkg.install \
_build/mytool _build/prefix
π ARGUMENTS π
PREFIX(required) β this is the install prefix, bestie. for example/usr/local. iconic.TOOLEXEC[:NAME](required) β TOOLEXEC is the tool executable. it gets searched in thePATHunless you give an explicit file path. NAME is the tool name, and if you don't specify it, it's derived from TOOLEXEC by taking the basename and stripping any.exeextension. also: repeatable π β you can stack these, go off.
β¨ OPTIONS β¨
--dry-runβ do not install, just output the paths that would be written. peek, don't touch π--mandir=MANDIR(absent=SHAREDIR/man) β MANDIR is the root man directory to install to.-sSHELL,--shell=*SHELL*(absent=All supported shells) β SHELL is the shell to support, and it must be one ofbash,zshorpwsh. repeatable, so you can collect them all like PokΓ©mon π--sharedir=SHAREDIR(absent=PREFIX/share) β SHAREDIR is the share directory to install to.--standalone-completionβ generate standalone completion scripts. these scripts do not depend on the generic cmdliner completion scripts. heads up tho: for some shells this may result in slower completion π (worth it? you decide, bestie)--update-opam-install=PKG.installβ update or create an opam.installfilePKG.installwith install moves from the installed files to the corresponding opam install sections. and yes, this also happens if--dry-runis specified π so like, not fully dry, iykyk.
π COMMON OPTIONS π
--help[=FMT](default=auto) β show this help in format FMT. the value FMT must be one ofauto,pager,grofforplain. withauto, the format ispagerorplainwhenever theTERMenv var isdumbor undefined.--versionβ show version information. iconic, brief, we love her β
π₯ EXIT STATUS π₯
cmdliner install tool-support exits with:
0β on success. we love a happy ending π123β on indiscriminate errors reported on standard error.124β on command line parsing errors. (typo era π)125β on unexpected internal errors (bugs). if you see this one, it's not you, it's them π
π SEE ALSO π
cmdliner(1)β go read the main one, bestie, it's the parent fr fr
okay that's the whole page!! this was Cmdliner v2.1.1, and honestly? she ate. go install some tool support, stay hydrated, and remember: dry-run first, queen πΈπ
β¨
π¦ where this page comes from
- arch rolling: ocaml-cmdliner 2.1.1-1 Β· ISC
- nixos 26.05: cmdliner 2.1.1
- nixpkgs unstable: cmdliner 2.1.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms