I've played bzflag for a couple of years and decided I should make a plugin for it. After some fooling around, it seems like a few configure options is missing. The options --enable-shared --enable-plugins are mandatory to use plugins with bzflag. After building the package manually, indeed, the plugin system worked, but without it, the wrong files are generated (.la files instead of .so files). Reproducible: Always Steps to Reproduce: 1. Emerge any version of bzflag with any set of use flags Actual Results: The server is built without the correct plugins files. Expected Results: The server is built with the correct .so plugin files.
Personally I'm not going to implement that: 1) I don't like the way plugins are implemented. They run in a uncontrolled environment, and it is easy to break the server with a malfunctioning plugin 2) I don't like to get bug reports because a plugin access wrongly to the bzflag server memory. 3) If you can build plugins, you have all the tools and probably expertize to build a server from source. When/if bzflag implement plugins with an interpreted engine, or other way that invalidated the problems I told, I'm ready to reconsider it.
