In order to build a thin plugin, make sure your plugin ends in the extension “.xpl”. The obvious downsides of this are that you have to distribute a different plugin for each operating system, and you don’t get a plugin “home” directory to pack your resources. (Originally thin plugins were just called “plugins”.) Thin plugins are the only packaging supported by the 1.0 API. All auxiliary files (image files, etc.) must be kept outside the plugin. xpl, which is dropped into X-Plane’s Resources\plugins\ directory. Packaging Thin PluginsĪ “thin” plugin is the original way of packaging plugins: the plugin consists of a single DLL with the extension. xpl, as dictated by SDK conventions, not the native platform. Note that in all of these cases the plugin’s extension is. Shared Dynamic Libraries (.dylib) for macOS.We will use the term DLL generically to mean a shared library of the appropriate type for your chosen ABI. While these have different names on different operating systems, the concept is the same: code that is linked into X-Plane while it is running. Plugins are DLLs (dynamically linked libraries). If they are not present, your plugin will receive a NULL return value and can take a fallback path. If you’re building a backward-compatible plugin (say, for both X-Plane 10 and 11), you can link against the 2.0 API and use the XPLMFindSymbol() utility to optionally fetch newer APIs. If you’re just starting out, we recommend using the SDK 3.0 API and defining XPLM200, XPLM210, and XPLM300. Likewise, if you define the symbol XPLM210, you’ll have access to the 2.1 API and your plugin will only work on X-Plane 10 and newer.įinally, if you define the symbol XPLM300, you’ll get access to the 3.0 API, and your plugin will work X-Plane 11.10 and newer. If you define the symbol XPLM200, then the 2.0 API will be available to your code, and your plugin will only work on X-Plane 9 and later. By default your plugin will only be able to use 1.0 APIs and run on any version of X-Plane. You can use the latest SDK download to build your plugin no matter what version of the API you are targeting. Plugins are almost the same for all APIs a few exceptions for compiling and linking 2.0+ plugins will be noted. 3.0 API is supported by X-Plane 11.10 and newer, is a superset of the 2.1 API.2.1 API is supported by X-Plane 10.00 and newer, is a superset of the 2.0 API.2.0 API is supported by X-Plane 9.00 and newer, is a superset of the 1.0 API.1.0 API is supported by X-Plane 6.70 and newer.There are three revisions of the X-Plane plugin API: This article covers issues of building and packaging plugins. X-Plane supports plugins for all three operating systems (macOS, Windows, and Linux). (The exact method of installation depends on the plugin, but for many plugins, you can simply drop the plugin directory into your Resources\plugins\ directory.) If you’re a user just trying to install a plugin, please see the “Expanding X-Plane” section of the X-Plane manual. Note: This article is for plugin developers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |