lopsubgen(1)

πŸ’… lopsubgen β€” the glow-up machine

okay so bestie, welcome to lopsubgen, and yes it lives in section 1, the User commands corner of the manual πŸ’–. Think of it as the makeover station for your lopsub suite: it takes your suite and turns it into C or roff, no cap.


✨ SYNOPSIS ✨

lopsubgen  [--help] [--version] [--output-dir=<dir>] [--gen-c[=<path>]]
[--gen-header[=<path>]] [--gen-man[=<path>]] [--version-string=<string>]

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe: lopsubgen reads a lobsub suite from stdin and converts it into zero or more output formats. Zero is a real number here, bestie β€” if you don't name any output format, the input just gets a vibe check for syntactic correctness and that's it. πŸ’…

The format of the input (the lopsub suite) is described in lopsub-suite(5). Go read it, iykyk πŸ“–


πŸŽ€ OPTIONS πŸŽ€

🌸 General options 🌸

  • -h, --help β€” print help and exit. And listen β€” give it twice and you get the detailed help. yes, twice. it's giving easter egg πŸ₯š
  • -V, --version β€” print version and exit. iconic, brief, love her.
  • -o, --output-dir=<dir> β€” where to write the output file(s). default: . β€” meaning all output files land in the current working directory unless you say otherwise 🏠
  • --gen-c[=<path>] β€” generate C output πŸ”₯ This produces a C file containing the definition of a subsub suite structure.

If <path> is absolute, the output goes to that exact path and the argument to --output-dir is ignored (yes, completely ignored, she does not care). Otherwise the output path is relative to the value of the --output-dir option.

If you don't pass the optional argument at all, the output file name is derived from the suite name by appending the string .lsg.c β€” cute, automatic, done πŸ’«

  • --gen-header[=<path>] β€” generate a .h file ✨ The generated header file is meant to be included from the application. It defines handy C enums and preprocessor macros, like the number of commands defined in the suite. so useful, honestly 🫢

The path for the generated header file is determined the same way as for C output β€” peep --gen-c.

🧚 Options for man output 🧚

  • --gen-man[=<path>] β€” generate the man page πŸ“–
Heads up bestie: if this option isn't given, all the subsequent options in this section are ignored. literally all of them. don't come crying 😭

The path for the output file is determined the same way as for C output β€” again, see --gen-c.

  • --version-string=<string> β€” override the version string πŸ’œ

If this option is given, its argument is used as the version string and the value of the version-string directive of the suite is ignored. Super useful for applications which dynamically create the version string by running a command like git-describe β€” yes, that git-describe. slay 🌈


Written by Andre Noll Copyright (C) 2016 Andre Noll License: GNU GPL version 3, http://www.gnu.org/licenses/gpl-3.0.html

This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Report bugs to Andre Noll πŸ›


🌈 SEE ALSO 🌈

Homepage: http://people.tuebingen.mpg.de/~maan/lopsub 🏑


and that's the whole page, bestie β€” this was lopsubgen, version 1.0.4, dated March 2024 πŸ’–βœ¨ go forth and generate πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from