The plugin template is meant to be used as a starting point for OBS Studio plugin development. It includes:
- Boilerplate plugin source code
- A CMake project file
- GitHub Actions workflows and repository actions
| Platform | Tool |
|---|---|
| Windows | Visal Studio 17 2022 |
| macOS | XCode 16.0 |
| Windows, macOS | CMake 3.30.5 |
| Ubuntu 24.04 | CMake 3.28.3 |
| Ubuntu 24.04 | ninja-build |
| Ubuntu 24.04 | pkg-config |
| Ubuntu 24.04 | build-essential |
An absolute bare-bones Quick Start Guide is available in the wiki.
All documentation can be found in the Plugin Template Wiki.
Suggested reading to get up and running:
Default GitHub Actions workflows are available for the following repository actions:
push: Run for commits or tags pushed tomasterormainbranches.pr-pull: Run when a Pull Request has been pushed or synchronized.dispatch: Run when triggered by the workflow dispatch in GitHub's user interface.build-project: Builds the actual project and is triggered by other workflows.check-format: Checks CMake and plugin source code formatting and is triggered by other workflows.
The workflows make use of GitHub repository actions (contained in .github/actions) and build scripts (contained in .github/scripts) which are not needed for local development, but might need to be adjusted if additional/different steps are required to build the plugin.
Successful builds on GitHub Actions will produce build artifacts that can be downloaded for testing. These artifacts are commonly simple archives and will not contain package installers or installation programs.
To create a release, an appropriately named tag needs to be pushed to the main/master branch using semantic versioning (e.g., 12.3.4, 23.4.5-beta2). A draft release will be created on the associated repository with generated installer packages or installation programs attached as release artifacts.
Basic concepts of codesigning and notarization on macOS are explained in the correspodning Wiki article which has a specific section for the GitHub Actions setup.