I am in the region which cannot access github.com directly, so when I use some technical method clone this repo, it always failed when pull the prebuilt binary in the directory cmake-build-debug. I think the prebuilt binary should publish via the release function of GitHub rather than directly include it in the VCS. It is really frustrated after pulling the extremely huge (compared with my poor bandwidth) file over and over again.
I am in the region which cannot access github.com directly, so when I use some technical method clone this repo, it always failed when pull the prebuilt binary in the directory
cmake-build-debug. I think the prebuilt binary should publish via the release function of GitHub rather than directly include it in the VCS. It is really frustrated after pulling the extremely huge (compared with my poor bandwidth) file over and over again.因为一些原因我需要利用一些技术手段克隆代码，但是在
cmake-build-debug下的预编译的二进制文件对我的小水管（4Mbps）来说太大了。我觉得或许将预编译的二进制文件放在releases功能里发布会比直接加到源码管理系统里更好一些。一次次地克隆和失败确实令人沮丧。