Glossary

Default Global Installation Path

This is the system-wide path where the REAPER binary executable is installed. This is different for each supported platform:

• Linux:
  • A global default is not predictable since Linux does not have a canonical package manager. Instead, cargo-reaper uses the which crate's which::which_global function to determine its location.
• Darwin (MacOS) -- /Applications/REAPER.app
• Windows:
  • x86 (32bit) -- C:\Program Files (x86)\REAPER\reaper.exe
  • x86_64 (64bit) -- C:\Program Files\REAPER (x64)\reaper.exe
  • aarch64 (ARM) -- C:\Program Files\REAPER (ARM64)\reaper.exe

Extension Plugin

A C/C++ dynamically linked library that when placed in REAPER's UserPlugins directory, is loaded as part of the REAPER application thread on launch, adding additional functionality to the program.

Dynamically Linked Library

A compiled collection of code and data that is loaded into a program at runtime, rather than being statically included in the final executable during compilation.

REAPER extension plugins are dynamically linked libraries, which have differing extension names depending on their target platform:

• Linux -- .so
• Darwin (MacOS) -- .dylib
• Windows -- .dll

User Plugins

The UserPlugins directory is the file system location created the first time REAPER is launched that the REAPER application thread loads extension plugins from. This is different for each supported platform:

• Linux -- ~/.config/REAPER/UserPlugins
• Darwin (MacOS) -- ~/Library/Application\ Support/REAPER/UserPlugins
• Windows -- %APPDATA%\REAPER\UserPlugins

Plugin Manifest

A plugin manifest, in the context of cargo-reaper, is the same as a Cargo manifest, which contains a package with a library target of crate-type cdylib.

See the Plugin Manifest section for detailed information on configuring a cargo-reaper plugin manifest.