These are the changes I made when I first tried to get the pktriggercord make file to compile a library version. I didn't get around to having it install the library or deal with packaging. I think part of the reason I eventually gave up was I wasn't quite sure what the preferred install/packaging behavior should be. That, and I didn't think the library would be very user-friendly without moving all of the code into a unique namespace, which I didn't feel up to doing at the time.
(The libpktriggercord package I eventually produced for INDI used a stripped down version of the source code and cmake to build/install. So that obviously wouldn't integrate well back into the original code base at the moment).
Thanks @karlrees for the pull requestl. Added this to the libpktriggercord branch and opened an issue for that: #49 let's continue the discussion there, I close this pull request now.
Initial support for library version.
These are the changes I made when I first tried to get the pktriggercord make file to compile a library version. I didn't get around to having it install the library or deal with packaging. I think part of the reason I eventually gave up was I wasn't quite sure what the preferred install/packaging behavior should be. That, and I didn't think the library would be very user-friendly without moving all of the code into a unique namespace, which I didn't feel up to doing at the time.
(The libpktriggercord package I eventually produced for INDI used a stripped down version of the source code and cmake to build/install. So that obviously wouldn't integrate well back into the original code base at the moment).