Sep 13, 2019

I'm trying to understand the libbitcoin's dependency chain. I will talk about the client stack. Libbitcoin-explorer has libbitcoin-system as a (indirect) dependency, which in turn has another (optional) icu dependency. For this reason I can build libbitcoin-explorer with icu option, it makes sense. Let's say I just want to build only the libbitcoin-network. The libbitcoin-network build (same for protocol and client) doesn't provide the icu option. Do I understand it correctly, that it was meant that way? In other words the libbitcoin-network (as well as protocol and client) doesn't use any icu features of libbitcoin-system and that is the reason I shouldn't build libbitcoin-network with icu option, right? (ICU was just an example, you can replace it with another optional dependency like png).