summaryrefslogtreecommitdiff
path: root/t/t4204-patch-id.sh
diff options
context:
space:
mode:
authorLibravatar Dennis Ameling <dennis@dennisameling.com>2021-03-29 12:41:45 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-03-29 13:49:04 -0700
commit958a5f5dfe4dda4fd59af30c1d58abe43ff19d6e (patch)
treef331333b487d98360bfa3a39384c7b29104a3e90 /t/t4204-patch-id.sh
parentcmake: add a preparatory work-around to accommodate `vcpkg` (diff)
downloadtgif-958a5f5dfe4dda4fd59af30c1d58abe43ff19d6e.tar.xz
cmake(install): include vcpkg dlls
Our CMake configuration generates not only build definitions, but also install definitions: After building Git using `msbuild git.sln`, the built artifacts can be installed via `msbuild INSTALL.vcxproj`. To specify _where_ the files should be installed, the `-DCMAKE_INSTALL_PREFIX=<path>` option can be used when running CMake. However, this process would really only install the files that were just built. On Windows, we need more than that: We also need the `.dll` files of the dependencies (such as libcurl). The `vcpkg` ecosystem, which we use to obtain those dependencies, can be asked to install said `.dll` files really easily, so let's do that. This requires more than just the built `vcpkg` artifacts in the CI build definition; We now clone the `vcpkg` repository so that the relevant CMake scripts are available, in particular the ones related to defining the toolchain. Signed-off-by: Dennis Ameling <dennis@dennisameling.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4204-patch-id.sh')
0 files changed, 0 insertions, 0 deletions