SO I have this library that I use in some other projects
 basically what happened was that I realized that C++ has no good database libraries for high level abstraction with postgresql (or probably any SQL databases, for that matter). I did find that the most robust, mature and supported library, that's actively being worked on, and even seems to posit itself as the "official" C++ Postgresql library, was libpqxx. But I didn't want to write my own queries in the code, so I went about making a few sets of overloaded methods for variations of queries etc. This wasn't a planned library, it was mostly just something I built out of necessity so I could avoid having to write even more extra code than I'm used to writing, which is already more than enough code for a given task.

 That said, I've developed a usable library over the course of a year or so, and I'm not sure if I want to refactor it, rewrite it, or just tune it. Adding some google testing to it would be a fine way of allowing me to get a better understanding of it and improve my cognitive acuity. In a sense, I'm able to test its logic and reliability, and become more intimate with it such that I'll be able to make a better decision about how best to make use of the general concept of abstracting libpqxx.

So the first thing we have to do is get it to compile.

Since we already use CMake on distant-vdi, as it stands, and because my first job of building it involved getting it into a library like Distant-VDI, where it has the CEF dependency, I quickly decided on the CMake route.

So here's a little