PROGEN(1)

πŸ“¦
version 0.12.0 Β· 4 versions
, in debian trixie, ubuntu noble, ubuntu questing

πŸ’– PROGEN(1) πŸ’–

okay bestie, welcome to the manual page for progen β€” the project generator that lives in your terminal and is, no exaggeration, that girl. this is the User Commands section, and we are about to get you fully caught up. no cap. ✨


✨ NAME ✨

progen β€” generate and manage project files for embedded development tools πŸ› οΈπŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

progen [GLOBAL_ARGUMENT] COMMAND [ARGUMENTS]

🌸 DESCRIPTION 🌸

so here's the vibe: progen lets you define an embedded project in text (YAML) files and then generate IDE-specific project files based on the rules defined in these records. that's it. that's the whole serve. write it once in YAML, let progen do the rest, main character energy only. πŸ’–


πŸŽ€ GLOBAL ARGUMENTS πŸŽ€

progen supports the following global arguments for all the commands listed below, so these are like the universal accessories that go with every outfit:

  • -v β€” increase verbosity of output (repeat for even more verbose output) πŸ—£οΈ
  • -q β€” decrease verbosity of output (repeat for even less verbose output) 🀫

πŸ‘‘ COMMANDS πŸ‘‘

🧚 init

progen init -p PROJECT -tar TARGET_NAME [-dir SCAN_DIR] -o OUTPUT_DIR [-v | -q]

Add progen support to a project β€” literally the glow-up command. ✨

If you want progen support for a project, this is the command to use. It scans the repository for files and creates 2 YAML files:

  1. the main project file (projects.yaml), and
  2. a project YAML file

In the project YAML file, there are all sources/includes and other project-related settings which progen finds in the repository. This creates a valid progen project file if a folder contains one valid project. In the case there are many, this command can serve at least as guidance β€” edit and move the YAML file accordingly to a folder structure to split projects. lowkey a starter kit, highkey a lifesaver. 🫢

Arguments

  • -p β€” project name
  • -tar β€” target name for the project
  • -dir β€” directory to scan (default: none; scan all in directory progen was executed in)
  • -o β€” directory for generated files
  • -v β€” increase verbosity of output (repeat for even more verbose output)
  • -q β€” decrease verbosity of output (repeat for even less verbose output)

πŸ¦‹ generate

progen generate -f FILE [-p PROJECT] [-t TOOL] [-b] [-c] [-o OPTIONS] [-j JOBS] [-v | -q]

Export defined projects β€” the moment where your YAML becomes real files, it's giving manifestation. πŸ”₯

Arguments

  • -f FILE β€” path to projects.yaml file
  • -p PROJECT β€” name of the project to generate. If not specified, all projects within projects in projects.yaml are exported
  • -t TOOL β€” tool name (uvision, iar, etc). If not specified, tools are checked in records (tool_supported)
  • -b β€” build the exported project (note: not every tool supports building a project) ⚠️
  • -c β€” copy all files defined for a project to exported directory
  • -o OPTIONS β€” toolchain options
  • -j β€” number of concurrent jobs to use for generating projects (default is 1; not supported by all tools)
  • -v β€” increase verbosity of output (repeat for even more verbose output)
  • -q β€” decrease verbosity of output (repeat for even less verbose output)

🌈 build

progen build -f FILE [-p PROJECT] [-t TOOL] [-c] [-k] [-o OPTIONS] [-x] [-j JOBS] [-v | -q]

Export a project, then build it. Note that not all tools support building β€” so pls check before you come for it. πŸ’€

Arguments

  • -f FILE β€” path to projects.yaml file
  • -p PROJECT β€” name of the project to build (if not specified, all projects within projects in projects.yaml are built)
  • -t TOOL β€” build project files for specified tool
  • -c β€” copy sources (as it exports first, this is used for exporting prior to building)
  • -k β€” clean project before building
  • -o OPTIONS β€” toolchain options
  • -x β€” stop on first failure πŸ›‘
  • -j β€” number of concurrent build jobs (default is 1; not supported by all tools)
  • project β€” specify projects to be generated and built
  • -v β€” increase verbosity of output (repeat for even more verbose output)
  • -q β€” decrease verbosity of output (repeat for even less verbose output)

πŸ“ list

progen list targets [-v | -q]

progen list tools [-v | -q]

progen list -f FILE projects [-v | -q]

List targets, tools or projects β€” the window-shopping command, obsessed. πŸ›οΈ

Arguments

  • targets β€” list all supported targets
  • tools β€” list all supported tools
  • projects β€” list all projects the repository supports (requires -f argument specified)
  • -f FILE β€” path to projects.yaml
  • -v β€” increase verbosity of output (repeat for even more verbose output)
  • -q β€” decrease verbosity of output (repeat for even less verbose output)

πŸ’œ clean

progen clean -f FILE -p PROJECT [-t TOOL] [-v | -q]

Remove progen files/folders β€” the spring cleaning episode. 🧹

This command removes progen-related files/folders. If progen generates data to various folders (for example, a per-project directory somewhere), this command will remove those folders.

Arguments

  • -f FILE β€” path to projects.yaml file
  • -p PROJECT β€” the project name which should be cleaned (removed)
  • -t TOOL β€” the tool name (if not specified, tools are taken from tools_supported)
  • project β€” specify projects to be cleaned (removed)
  • -v β€” increase verbosity of output (repeat for even more verbose output)
  • -q β€” decrease verbosity of output (repeat for even less verbose output)

⭐ TOOLS ⭐

progen supports generating projects for the following tools β€” the whole roster, and every single one of them ate:

  • uVision4 and uVision5
  • IAR
  • Makefile (GCC ARM)
  • Makefile (ARMCC)
  • Cmake (GCC ARM)
  • CoIDE (GCC ARM)
  • Eclipse (Makefile with GCC ARM)
  • Sublime (Makefile with GCC ARM)
  • Visual studio (Makefile with GCC ARM)

πŸ’… EXAMPLES πŸ’…

To generate a uvision project file for the k20d50m_blinky target:

progen generate -f projects.yaml -p k20d50m_blinky -t uvision

look at that. one line. iconic behaviour. πŸŽ€


Copyright 2014-15 Martin Kojtal


🫢 AUTHOR 🫢

This manual page is based on the progen documentation. It was created by Nick Morrott <nickm@debian.org> for the Debian GNU/Linux system, but may be used by others. ty bestie for your service. πŸ’–


🌈 SEE ALSO 🌈


and that's the whole page, bestie. go forth and generate. πŸ’…βœ¨

version 0.12.0 β€” dated February 2021 🌸 β€” no cap, that's genuinely the version and date this page is signed off with, so if you were looking for the receipts, there they are. bye bestie, ily, go build something πŸ’–πŸ¦‹πŸ‘‘

πŸ“¦ where this page comes from