The plugins inside the folder have the specific names win.xpl, mac.xpl and lin.xpl. In order to build a thin plugin, make sure your plugin ends in the extension ".xpl".Ī "fat" plugin is a folder containing one or more plugins. (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.Ī "thin" plugin is the original way of packaging plugins: the plugin consists of a single DLL with the extension. So a Windows plugin is a DLL with the extension. Note that in all of these cases the plugin's extension is dictated by SDK conventions, not the native platform. Shared Dynamic Libraries (.dylib) for Mach-O on OS X.We will use the term DLL generically to mean a shared library of the appropriate type for your chosen ABI. Plugins are DLLs (dynamically linked libraries) 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. One way to use the 2.1 API is to link against the 2.0 API and use XPLMFindSymbol to optionally fetch 2.1 APIs - if they are not present, your plugin will receive a NULL return value and can take a fallback path. The 2.0 API has a utility routine XPLMFindSymbol. Note: if you want to use the 2.1 APi, define XPLM210 and XPM200! If you define the symbol XPLM210, then the 2.1 API will be available to your code, and your plugin will only work on X-Plane 10 and later. ![]() 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 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 both APIs a few exceptions for Compiling and linking 2.0 plugins will be noted. 2.1 API is supported by X-Plane 10.00 and newer, is a super-set of the 2.0 API.2.0 API is supported by X-Plane 9.00 and newer, is a super-set 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: There is no 64-bit build of X-Plane for PPC Macs. x86_64 is required for 64-bit X-Plane, i386 is required for 32-bit X-Plane on Intel CPUs, and ppc is supported for 32-bit PPC machines (X-Plane 9 and earlier). Only users who have a CPU matching a code type in your plugin will be able to load your plugin. ![]() You can combine these formats in a single Mach-O plugin, or support only the CPUs you care about. Mach-O plugins can contain one or more supported CPU formats over time X-Plane has supported ppc, i386, and x86_64. Mach-O plugins can be built as OS X "bundles", but it is strongly recommended that your plugin be a single Mach-O dynamic library file. This document only covers building Mach-O plugins this format works with X-Plane 7.63, 8, 9 and 10. This chapter covers issues of building and packaging plugins. X-Plane supports plugins for all three operating systems (OS X, Windows, and Linux).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |