> Historically the dependency management tool for C++ is the system's package manager, and/or a shell configure/provision script. I agree with you here. The sy

> Historically the dependency management tool for C++ is the system's package manager, and/or a shell configure/provision script. I agree with you here. The system package managers where invented to solve system global dependency problems between libraries/executables as well as provide headers and static libraries for development on the current machine. > I don't see any value add to a "built in" dependency management tool to C++. Not as in it isn't a useful thing to have, just that it can't solve the big problem which is that most C++ projects would never support it. Even if you don't see a need, you have to acknowledge that many other people see the need to have some sort local dependency management, be it compile time like cargo or the different cross-build environments (openembedded, buildroot, co.) or runtime like chroots, containers, virtual machines. It can be argued that the local dependency management solutions are in their infancy.