Recommended inclusion method?

[chintal]

I used the raspidmx library a couple of years ago to make a small program that draws rectangles on the screen. ( https://github.com/chintal/raspi-backdrop ) At the time, the raspidmx build scripts produced a .so which I copied to the /usr/local/lib and then used it as any other library.

With the current build scripts, however, I see there is only a .a generated for static linking. I see #16 and e2ee6faa, which is where the change seems to have been made.

Is there a recommended / preferred way to include raspidmx in other programs? It would be nice to have one mechanism which is explicitly chosen and will continue to be viable.

Options, as I see them, could be :

• Copy the library code directly into the application code and just maintain the copy there. Personally, I'd want to avoid this.
• Build the .a, manually copy the .a into the application code base or otherwise get it into the appropriate library search path. Given this involves a fair amount of manual tweaking and/or setting environment variables, I'd like to avoid this if possible.
• As before, build a .so. The .so can be installed to the system either manually or using make install, and used by applications.
• Build a .so, pack it into a debian package, so that it can be installed using dpkg or added to a repository (debian / rasbian / somewhere) and installed using apt.