2013-01-21, 20:56
I am just jumping into XBMC add-on development and I am curious what the accepted/typical way that Python library dependencies are managed in add-ons?
I've started playing around with the Soundcloud music add on and want to make it leverage the Soundcloud SDK (https://github.com/soundcloud/soundcloud-python). I am planning on including the SDK library with the add-on, but the SDK has additional dependencies that I'm not sure how to deal with, such as the Python 'Requests' library (http://docs.python-requests.org/en/latest/). Should I have the add-on look for the existence of those libraries and if they don't exist, install them some how? If so, what is the best way to do this in a cross-platform kinda way? Should I include the dependent libraries/versions with the add-on source? Or should I do this completely differently? Thanks!
I've started playing around with the Soundcloud music add on and want to make it leverage the Soundcloud SDK (https://github.com/soundcloud/soundcloud-python). I am planning on including the SDK library with the add-on, but the SDK has additional dependencies that I'm not sure how to deal with, such as the Python 'Requests' library (http://docs.python-requests.org/en/latest/). Should I have the add-on look for the existence of those libraries and if they don't exist, install them some how? If so, what is the best way to do this in a cross-platform kinda way? Should I include the dependent libraries/versions with the add-on source? Or should I do this completely differently? Thanks!
