NAME
SYNOPSIS
DESCRIPTION
OPTIONS
rusty − small and fast build system for C, C++ and possibly more
rusty [−h] [−−help] [−−ast] [−−info] [−−about] [−viratwn] [−o DIR] [−−output DIR] [−d DIR] [−−dir DIR] [−c COMPILER] [−−compiler COMPILER] [−o DIR] [TARGETS] [clean] [install] [uninstall]
rusty is a simple build system, which borrowed its core syntax from C2’s built-in build system. Rusty uses Daniel Holden’s (orangeduck’s) mpc. At the moment, rusty can handle four types of targets: executables, shared and static libraries and object-code only targets. Rusty requires a rustyfile (rusty.txt) somewhere in the cwd path. Rusty searches for it recursively, so you don’t have to worry about executing it from your projects’ subdirectories.
−h, −−help
Print a basic help text.
−−about
Print a basic about text with even more basic usage example.
−c, −−compiler name
Change the compiler used to process files.
−i, −−info
Print info about each target found in the rustyfile.
−d, −−dir path
Change directory before looking for rustyfile.
−r, −−fullrebuild
Recompile all files regardless of whether or not has it been modified. Useful if compilation fails, becau 5828 se atm, Rusty can’t detect if the compilation has failed or not.
−o, −−output path
Change the output directory for targets
−t, −−time
Measure and print the CPU clock time rusty’s execution took. Note that the CPU time is much shorter than the total time execution took.
−n, −−check
Just check the rustyfile and don’t compile or build anything. Other command−line arguments still processed.
−w, −−wanted−only
Show info & ast only for desired targets, not the whole rustyfile. usage of −i and −a is still required for the information to show.