2021-05-07, 07:26
Basically, a kodi binary addon consists of a C(++) library that uses Kodis C(++) API. There are several types of addons, implementing different functions inside kodi, e.g. PVR, Visualizations, Screensavers, VFS(Virtual File System)..
There is no "classic" binary addon, just different specializations.
An addon can have it's own external dependencies, independent of kodi itself.
Everything inside a binary addon source code must be human readable, including all dependencies. This is also true for python addons.
Kodi's binary addon build system handles building such external dependencies from source, so you would link against libtorrent, not include it's source code directly.
Take a look at the API docs:
https://alwinesch.github.io/group__cpp__...__vfs.html
https://alwinesch.github.io/group__cpp__..._defs.html
Example: https://github.com/xbmc/vfs.rar/blob/Mat.../RarFile.h
And here is an example how to add external library dependencies: https://github.com/xbmc/vfs.rar/tree/Mat...on/tinyxml
Since libtorrent uses cmake already, simply suppling the URL to the source tarball could be enough.
There is no "classic" binary addon, just different specializations.
An addon can have it's own external dependencies, independent of kodi itself.
Everything inside a binary addon source code must be human readable, including all dependencies. This is also true for python addons.
Kodi's binary addon build system handles building such external dependencies from source, so you would link against libtorrent, not include it's source code directly.
Take a look at the API docs:
https://alwinesch.github.io/group__cpp__...__vfs.html
https://alwinesch.github.io/group__cpp__..._defs.html
Example: https://github.com/xbmc/vfs.rar/blob/Mat.../RarFile.h
And here is an example how to add external library dependencies: https://github.com/xbmc/vfs.rar/tree/Mat...on/tinyxml
Since libtorrent uses cmake already, simply suppling the URL to the source tarball could be enough.
