Native extensions: where to start
Routes to a working example, library descriptor and interface data.
Use this section when you need a native library, a language binding or direct C ABI access. For ordinary game logic start with C#; custom files and PCM often need only existing overridable APIs without a native build.
Routes by task
| Task | Read |
|---|---|
| Understand an extension’s structure and limits | Native extension contract |
| Configure a DLL, entry point and platform features | The .reckfellextension file |
| Build a small first C17 example | C example and loading checks |
| Build the existing C++ example with MSVC/CMake/SCons | Native builds |
| Obtain binding-generator data | Interface JSON and C header |
| Decide whether a native extension is needed | Choosing an API |
Recognize a working result
First prove one complete path: the library builds for your OS/architecture, the manager loads its descriptor, the expected class and constant appear, and unloading removes the registration. The C and C++ examples demonstrate that check.
It does not establish concrete instance implementations, every method, performance, hot reload or other-platform exports. Next add the required function and independently check its data, ownership and game-side call. Opening a DLL alone is not a basis for universal compatibility promises.