2015-05-08, 17:14
by the way, if you're actually dev'ing the viz with my fork, the easiest way is
1) build kodi somewhere
2) configure the addon with -DCMAKE_PREFIX_PATH=<build_dir>/build -DKODI_BUILD_DIR=<build_dir>
that way it will use the platform libs etc from the kodi build dir, and whenever you execute 'make' in the visualization's build dir, it will mirror data and binaries in the kodi build dir for easy testing (just run out of the build dir and test..).
executing 'make' in kodi will keep the add-on bindings up to date, so no need copying those around manually either should you be changing those. it is all very convenient
note that you have to use the cmake buildsystem in project/cmake - i don't update the autotools system at all.
1) build kodi somewhere
2) configure the addon with -DCMAKE_PREFIX_PATH=<build_dir>/build -DKODI_BUILD_DIR=<build_dir>
that way it will use the platform libs etc from the kodi build dir, and whenever you execute 'make' in the visualization's build dir, it will mirror data and binaries in the kodi build dir for easy testing (just run out of the build dir and test..).
executing 'make' in kodi will keep the add-on bindings up to date, so no need copying those around manually either should you be changing those. it is all very convenient
note that you have to use the cmake buildsystem in project/cmake - i don't update the autotools system at all.