On 27.11.2019 18:56, Philip Oakley wrote:
I just bumped against a potential issue like this. I was test compiling
[1a,b] the `vs/master` branch from Git-For-Windows and got the LINK
error that the 'libcurl-d.lib' was not found (4 places).
Error LNK1104 cannot open file 'libcurl-d.lib' git-imap-send
C:\git-sdk-64\usr\src\git\git-imap-send\ LINK 1
Having just located this email, I changed the build type to 'Release'
and the errors disappeared.
Do we also need to identify where the libcurl-d.lib will be found? i.e.
is it something that needs including via the sdk pacman list (I think
I'm up to date but maybe not..)
A quick web search didn't show any hits for `libcurl-d.lib` (with the
dash `-`), though did find a few for `libcurld.lib`.
If you clone `git-for-windows` and build in VS using `git.sln`, it will
automatically clone `git-for-windows\compat\vcbuild\vcpkg` and build
various things there, resulting in
`git-for-windows\compat\vcbuild\vcpkg\buildtrees\curl\x64-windows-dbg\lib\libcurl-d.dll`
`git-for-windows\compat\vcbuild\vcpkg\installed\x64-windows\debug\bin\libcurl-d.dll`
`git-for-windows\compat\vcbuild\vcpkg\packages\curl_x64-windows\debug\bin\libcurl-d.dll`
Which will be picked up by solution to build git.
I have built Debug many times now and didn't have any issues. If you do,
I would suggest to clone a new copy and build it.
