Bitcoin full node and query server
Jun 9, 2026
View in context in the libbitcoin Slack #general mirror.
Vano Chkheidze14:35
clone repo as submodule configure all build flags turn off all futures you dont need and compile it as part of your source it have zero dependencies so will build without problem
3 replies · pmienk, Vano Chkheidze, evoskuil · last Jun 09, 2026
pmienk16:45
The model we've used for all other dependencies is to perform a configured installation and then relied on either cmake targets of pkg-config for linking while on windows/vs using nuget. I'm currently looking into your use of cmake as you install targets and a pc file (which is great for us supporting autotools and cmake), however you don't appear to install the generated library. I'm working though your targets to determine the best placement for this kind of change and making sure I understand what's going on within your recursive CMakeFile.txt files as I would not want to cause you any undue maintenance burden
👍 1
Vano Chkheidze16:47
if will be needed to fix something in cmake ping me any time or just send fix pr and will merge to repo for future use i'm open for any colaborations
👍 1
evoskuil17:52
We use these terms (sort of informally): Unit Test - smallest unit possible/practical (e.g. lowest level method/function). Component Test - aggregate of units (e.g. class or aggregating function/method). Functional Test - system function (e.g. endpoint communication over a socket, public API). Acceptance Test - performed over the compiled executable (e.g. customer acceptance). We target full Unit Test coverage and Component and/or Functional as necessary to ensure expected aggregate behavior. No external dependencies (e.g. Python or other tools), just Boost Test in our pattern. Can be data-driven (which is when we allow loops in a test). Acceptance is outside of the build (against the executable or compiled lib).(edited)