sourcey / pluga

Simple C++ cross-platform plugin system

Pluga

Simple C++ plugin system

Homepage: http://sourcey.com/pluga
Documentation: http://sourcey.com/libsourcey/api-pluga/
Dependencies: LibSourcey (base, uv)
Licence: LGPL

Pluga is a simple C++ plugin system that you can drop into your own projects. It currently supports:

• Loading cross-platform plugins and shared libraries
• Simple and elegant API for defining plugins
• Strict API versioning for ABI safety

For more information take a look at this blog post which talks about the concepts and mothodology behind Pluga.

Installing

• Install LibSourcey
• Clone the Pluga repository in the LibSourcey src folder:

cd libsourcey/src
git clone https://github.com/sourcey/pluga.git

• Ensure the BUILD_MODULE_pluga build variables are enabled in CMake and regenerate the LibSourcey project files
• To build Pluga tests also enable the BUILD_TESTS and BUILD_TEST_pluga variables in CMake

Contributing

Contributions in the form of pull requests are always welcome.

1. Fork Pluga on Github
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Issues

If you find any bugs or issues please use the Github issue tracker.

pluga's Issues

LGPL? Seriously?

With all due respect, your whole library doesn't really make more than 100 lines of code. It's a bunch of #ifdefs and a class, and you're publishing this with LGPL? Seriously? Are you surprised that only amateurs use your library, if ever? I will never understand developers that do what you're doing.

Consider changing the license to something less ridiculous and more useful, such as MIT or BSD.

Cheers!

How to prevent a crash inside plugin screwing up the main pipeline ?

Hi,

I am reading the implementation of pluga. I really like the clean interface and mechanism.

But in order to be a reliable plugin framework, how does the core system prevent crashes caused by 3rd party plugins ? I don't have a good idea right now. The only sane idea I can think of is making all plugins run in another process, then use IPC to communicate with. But then the communication part will be complicated and an bottleneck for data intensive applications.

Do you have any idea on this ?

Thanks,