obs-windows-building

Compile OBS Studio plugins on Windows with MSVC or MinGW toolchains.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/meriley/claude-code-skills --skill obs-windows-building
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obs-windows-building
Source: https://github.com/meriley/claude-code-skills/tree/main/skills/obs-windows-building
Command: npx skills add https://github.com/meriley/claude-code-skills --skill obs-windows-building

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and templates (resource) components.

What problem does it solve?

This Skill streamlines the process of building OBS Studio plugins specifically for the Windows operating system, handling the complexities of different compilers and system libraries.

Core Features & Use Cases

  • Compiler Support: Build plugins using either Microsoft Visual C++ (MSVC) or MinGW.
  • Symbol Export: Correctly exports necessary functions using .def files for dynamic loading by OBS.
  • Windows Libraries: Integrates essential Windows system libraries like ws2_32 and comctl32.
  • Platform-Specific Code: Manages conditional compilation for Windows-specific code paths.
  • Use Case: You are developing a new OBS Studio plugin and need to compile it for Windows users, ensuring all required functions are exported and system dependencies are correctly linked.

Quick Start

Use the obs-windows-building skill to build your OBS plugin for Windows using Visual Studio.

Frequently Asked Questions about obs-windows-building

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build OBS Studio plugins on Windows using MSVC or MinGW?

Building OBS Studio plugins on Windows requires configuring your CMake project for either MSVC or MinGW toolchains. This skill facilitates native compilation by managing platform-specific source files and ensuring cross-compiler compatibility.

Why does my OBS plugin fail to load on Windows due to missing exported symbols?

OBS plugins fail to load when functions are not exported. This skill resolves missing exported symbols by utilizing `.def` files for dynamic loading, ensuring OBS Studio correctly recognizes and imports required functions.

Do I need to manually link Windows system libraries like ws2_32 and comctl32 for OBS plugin development?

For OBS plugin development, linking system libraries like `ws2_32` and `comctl32` is required. This skill integrates these essential Windows libraries automatically, ensuring correct system dependency resolution during compilation.

What is the best way to manage platform-specific code paths when compiling OBS plugins for Windows?

Managing platform-specific code for OBS plugins requires conditional compilation. This skill manages Windows-specific code paths to ensure cross-compiler compatibility across MSVC and MinGW environments during native compilation.

Can I use CMake to compile an OBS Studio plugin for Windows using Visual Studio?

Yes, you can use CMake to compile an OBS Studio plugin for Windows using Visual Studio. This skill supports native compilation using the MSVC toolchain, handling system library linking and symbol exports.