Oct 11, 2019

My point yesterday was that for package manager, the way the Libbitcoin CMake files are designed makes package management complicated. So, from a build perspective, yes CMake will build successfully, from a packaging perspective it uses some constructs (such as global include and link path manipulation) that make life rather complicated. My issue specifically is that my package management solution is expecting a package named 'Bitcoin-System', but the CMake module is defining one named 'libbitcoin_system'. I can work around it to get CMake working, however, I have most of this working using autotools (which required its own set of hacks)