unreal-thirdparty
Expert guide for integrating third-party C/C++ libraries into Unreal Engine 5.x projects and plugins. Covers static linking, dynamic linking (DLL/SO/dylib), Build.cs configuration, ModuleType.External, delay loading, runtime dependency staging, wrapping patterns, cross-platform considerations (Windows/macOS/Linux), ABI compatibility, RTTI/exceptions, header inclusion with THIRD_PARTY_INCLUDES_START/END, and common pitfalls. Use when the user asks about adding external libraries, third-party code, linking .lib/.a/.dll/.so/.dylib files, Build.cs PublicAdditionalLibraries, PublicDelayLoadDLLs, RuntimeDependencies, ModuleType.External, wrapping a C++ library for UE, FPlatformProcess::GetDllHandle, cross-compiling libraries for UE on Linux, or troubleshooting linker errors / DLL load failures with third-party code.
maystudios · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add maystudios/claude-skills --skill unreal-thirdparty技能说明
name: unreal-thirdparty description: > Expert guide for integrating third-party C/C++ libraries into Unreal Engine 5.x projects and plugins. Covers static linking, dynamic linking (DLL/SO/dylib), Build.cs configuration, ModuleType.External, delay loading, runtime dependency staging, wrapping patterns, cross-platform considerations (Windows/macOS/Linux), ABI compatibility, RTTI/exceptions, header inclusion with THIRD_PARTY_INCLUDES_START/END, and common pitfalls. Use when the user asks about adding external libraries, third-party code, linking .lib/.a/.dll/.so/.dylib files, Build.cs PublicAdditionalLibraries, PublicDelayLoadDLLs, RuntimeDependencies, ModuleType.External, wrapping a C++ library for UE, FPlatformProcess::GetDllHandle, cross-compiling libraries for UE on Linux, or troubleshooting linker errors / DLL load failures with third-party code.
Unreal Engine Third-Party Library Integration -- C++ Guide
Official Documentation (always consult for latest details)
Additional Community Resources
Plugin Template
UE ships a Third Party Library plugin template. In the editor: Plugins > New Plugin > Third Party Library (scroll to bottom). This generates the scaffolding for a DLL-based integration. For static libraries, the two-line approach in Build.cs is simpler.
Core Architecture
See references/build-system.md for the full Build.cs reference with all properties and path variables.
Integration flow:
Third-Party Source (or prebuilt binaries)
|
v
[Optional: Recompile with UE toolchain for ABI compat]
|
v
Place headers + libs in Plugin/Source/ThirdParty/
|
v
Create External Module (.Build.cs with ModuleType.External)
|-- PublicIncludePaths -> header directories
|-- PublicAdditionalLibraries -> .lib / .a files
|-- PublicDelayLoadDLLs -> DLL names (Windows delay-load)
|-- RuntimeDependencies -> .dll / .so / .dylib staging
|-- PublicDefinitions -> preprocessor macros
v
Consumer Module depends on External Module
|-- PublicDependencyModuleNames.Add("MyThirdPartyLib")
|-- #include with THIRD_PARTY_INCLUDES_START/END
v
Use library API in UE C++ code
Recommended directory layout:
MyPlugin/
MyPlugin.uplugin
Source/
MyPlugin/ # Runtime module (your code)
MyPlugin.Build.cs
Private/
Public/
ThirdParty/
阅读完整来源 ↗