For functions that must have C linkage (to be callable from other languages like C# via P/Invoke), you can still use extern "C" alongside the macro:
In this article, we’ll dissect what xplatcppwindowsdll is, why the new update matters, and how you can leverage its features to build faster, safer, and truly cross-platform C++ binaries for Windows environments. For the uninitiated, xplatcppwindowsdll is a specialized build toolchain and library template designed to simplify the creation of Windows Dynamic Link Libraries (DLLs) from a single, cross-platform C++ codebase. xplatcppwindowsdll updated
XPLATCPP_PUBLIC MyClass& getInstance() static MyClass instance; // thread-safe in C++11 and later return instance; For functions that must have C linkage (to
The updated toolchain integrates clang-cl with the latest Visual Studio 2022 (17.8+) to produce ARM64 DLLs that are up to 35% more efficient in emulated x86 scenarios. The biggest headache—exporting symbols—has been eliminated. The new version introduces a XPLATCPP_PUBLIC macro that works flawlessly across MSVC, Clang, and GCC. we’ll dissect what xplatcppwindowsdll is
find_package(xplatcpp 3.0 REQUIRED) xplatcpp_windows_dll( TARGET MyEngine SOURCES engine.cpp PRIVATE_DEFINES _CRT_SECURE_NO_WARNINGS PUBLIC_DEFINES MYENGINE_EXPORTS WINDOWS_VERSIONINFO on LOAD_TIME_PROFILING off # optional, enable for debugging ) The new explicit TARGET and WINDOWS_VERSIONINFO parameters prevent ambiguous parsing. Replace your own export macros with #include <xplatcpp/api.h> and tag public classes/functions with XPLATCPP_PUBLIC .