vcpkgTools.xml is apparently not scalable

[am11]

Currently, I cannot build vcpkg on latest FreeBSD 12, as something in the dependency chain has updated by ports, that cmake/ninja rely on.

Therefore, I was trying to update dependency tools packages (cmake and ninja) for FreeBSD, and I could not figure out which one of the following approaches should be taken:

• build a new self-contianed FreeBSD cmake package, with all their subdependencies libarchive, libjsoncpp etc. (like currently @ivysnow has provided)
  • it requires continuous updates, as it breaks the newer version (as in the current form)
• grab txz from http://pkg.freebsd.org/freebsd:12:x86:64/latest/All/, and fetch each subdependency (libarchive, libjsoncpp etc.) individually
  • i have it working, but i don't think it is scalable either 🤷‍♂
• simply introspect subdependency list and echo "Please run sudo pkg install <missing dependencies list>, before running the bootstrap-vcpkg.sh".

I think the last option is much simpler and robust, and the callee script is already containing similar messages for other OS:

vcpkg/scripts/bootstrap.sh

Lines 67 to 68 in 9994cdf

	echo "Could not find $__tool. Please install it (and other dependencies) with:"
	echo "sudo apt-get install curl unzip tar"

In the same vein, if certain tools are considered prerequisite to run bootstrap-vcpkg.sh and users are required to download from package manager (aka a simple and scalable approach), what makes cmake and ninja so special that we need vcpkgTools.xml and its mechanics in bootstrap.sh?