![]() Each plugin library must be in its own subdiretory of the /modules directory. Stellarium is looking for plugins in the /modules subdirectory of the user data directory or the installation data directory. This is why adding a new static plugin requires either asking the developers to add it to the main distribution, or creating and distributing a custom build.ĭynamic plugin libriaries need to be installed in a proper place in Stellarium's file tree to function. Static plugins require changes in the core code of Stellarium (the addition of Qt macros in several classes). This is the reason why the official plugins have been linked statically to the official release. This is used to release fixed versions of some "official" plugins together with Stellarium's releases.Īs Stellarium's plugin interface has changed over time, plugins for different versions so far are not interchangeable. They become "built-in", a part of Stellarium's binary files. static plugins are linked statically at build-time. ![]() This allows dynamic plugins to be distributed separately from Stellarium. dylib on Mac OS X) that are loaded at run-time (on start-up) by Stellarium. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |