Den mån 12 aug. 2024 kl 23:21 skrev Timofei Zhakov <t...@chemodax.net>:
> What do you think about just removing this section? > > There is already a logging of how CMake looks for the dependencies and > of their versions, so I don't see any reason to duplicate it. > Providing an example of these logs below: > > [[[ > [...] > 1> [CMake] -- Found APR: > C:/tima/poshsvn-trunk/vcpkg_installed/x64/x64-svn-windows/lib/libapr-1.lib > (found version "1.7.4") > 1> [CMake] -- Found APRUtil: > > C:/tima/poshsvn-trunk/vcpkg_installed/x64/x64-svn-windows/lib/libaprutil-1.lib > (found version "1.6.3") > 1> [CMake] -- Found ZLIB: > C:/tima/poshsvn-trunk/vcpkg_installed/x64/x64-svn-windows/lib/zlib.lib > (found version "1.3.0") > 1> [CMake] -- Found EXPAT: > > C:/tima/poshsvn-trunk/vcpkg_installed/x64/x64-svn-windows/lib/libexpatMD.lib > (found version "2.2.6") > 1> [CMake] -- Found SQLiteAmalgamation: > C:/tima/svn-cmake/sqlite-amalgamation (found version "3.46.0") > 1> [CMake] -- Found Serf: > C:/tima/poshsvn-trunk/vcpkg_installed/x64/x64-svn-windows/lib/serf-1.lib > (found version "3.1.4") > [...] > ]]] > > Yeah, I added this section myself, but right now it no longer makes > sense for me :) > It's ok to change your mind :-) It adds some value when doing repeated builds. The [CMake] -- Found ... is only shown when CMake actually searches for the dependency, not when the dependency is loaded from the cache. But I don't know how common the repeated builds is, compared to build once. For me as developer it is, but for an end user? On the other hand probably everyone actually building themselves are some kind of developer (excluding those running Gentoo Linux or MacPorts, both distributing build scripts+source rather than binaries). I'm somewhat leaning towards keeping them, but I can easily be persuaded. I'd like to see someone else chime in as well. I know Nathan was talking about setting up a CMake build and I'd be interested to hear his experience. Kind regards, Daniel
