2015-04-23, 22:17
I'm ready to write my first plug-in to scratch a particular itch that I have - I've read the docs, looked at the source and it seems pretty straight forward (I've been writing C++ professionally since 1992 - so the actual writing of the plugin in no big deal).
I intend to keep the code in a git repo - probably pushed up to github ... and its around that which my question lies.
The guides suggest hacking the code directly in the roaming app data directory (or I guess under .kodi in linux). That doesn't feel right to me - I don't think I would want to have my git repo under there. How do people generally do this?
I would expect to be able to specify a plugin path which I could extend to include by development source (and to omit when running the system in 'production'). I guess in linux I could create a symlink from my repo location to the plugins folder. I could do this in windows too using an NTFS link - but I generally avoid them as they are difficult to manage.
Ian
I intend to keep the code in a git repo - probably pushed up to github ... and its around that which my question lies.
The guides suggest hacking the code directly in the roaming app data directory (or I guess under .kodi in linux). That doesn't feel right to me - I don't think I would want to have my git repo under there. How do people generally do this?
I would expect to be able to specify a plugin path which I could extend to include by development source (and to omit when running the system in 'production'). I guess in linux I could create a symlink from my repo location to the plugins folder. I could do this in windows too using an NTFS link - but I generally avoid them as they are difficult to manage.
Ian
