initial library, libinstall

[hanatos]

about -fPIE and -fPIC. vkdt uses the former, for a library build you'd need the latter. executables are built with -pie, so at the price some small overhead and at the cost of allowing symbol interposition, you'll probably want to replace

EXE_CFLAGS=-fPIE

by

EXE_CFLAGS?=-fPIC

where the question mark means to set it only in case a user didn't provide an override up front (say from config.mk).

[butcherg]

I just pushed a new commit to the branch, tested installation/clean to /usr/local, and compilation/link/run of libtest. User has to run sudo ldconfig after the install.

Thing is, as-is the libinstall target has to put data/ and modules/ in /usr/local/lib so the dlinfo() can provide a directory that resolves them. Maybe some search strategy that allows a subdirectory in fs_basedir(), e.g. first look in dlinfo_dir, then dlinfo_dir/vkdt?

Edit: sorry, forgot #pragma once in libvkdt.h. Committed and pushed...

[hanatos]

merged!

and adjusted a few things:

• unified the install rules in the makefile a bit, reusing stuff
• the basdir is now something/lib/vkdt if the lib is in something/lib, which is the same as if the install includes binaries in something/lib/vkdt/vkdt-cli
• basedir is probed, it uses binary/exe and tests for darkroom.ui. if it can't find it, it reverts to searching libvkdt.so
• renamed libvkdt.h to vkdt.h, using lib in a header file name seemed duplicate.

i suppose up next: write test code using the library and put it into a github action to make sure this code path does not rot over time.