(2015-11-27 11:39)wsnipex Wrote: This is because your PictureItConfig.cmake does not set PICTUREIT_LIB_DIR.Hm.. As of right now it works though.
I'll set up a LXC container on my NAS later today and set up a proper build-environment for binary addons
Not all the info I need, but it will get me started at least
(2015-11-27 11:39)wsnipex Wrote: - You should put your headers in in the src dir, right besides the cppsReally? I did a lot of googeling and most people said it's better to have the headers in a separate folder "include".
Having them side-by-side with the cpp's was what I had initially and than forced myself to restructure the whole project :/
(2015-11-27 11:39)wsnipex Wrote: - the depends dir is not meant to put headers or libraries directly. Its intended use is to put definitions(usually an URL to a tarball or github repo) of libraries, your addon needs. Our kodi cmake addon buildsystem will then automatically download and build those dependencies. This won't be used on standalone building(=clone addon repo, cmake, make install) though. In that case you have to install all needed dependencies (system wide) manually.Hm I see.
That's probably java shining through a bit as I like to have everything project related within my project.
So let's say PictureIt depends on stb_image.h and boost-filesystem (might have to used that in the future for dir-listing).
How would you go about managing/adding those dependencies?
For PictureIt itself I could say "boost is a necessary dependency, so install it if want to use PictureIt in your project"
For visualization.pictureit I have to have everything included meaning the depends-folder would have a link to boost-filesystem
and my CMakeLists.txt would link it?
Would it be okay to have stb_image.h somewhere in my project? If so, where would be the best place to put it?
I don't like putting external resources into my src (or include) dir. Personally I like to have things separated and well organized
btw, I pushed everything to github now
I know the structure of the visualization.picture dev branch is plain wrong but in my defense...
...It got late and my brain wasn't functioning properly anymore ^^