From: Philip Oakley <philipoakley@iee.email>
To: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>,
Alexandr Miloslavskiy via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] contrib/buildsystems: fix Visual Studio Debug configuration
Date: Thu, 28 Nov 2019 00:34:00 +0000 [thread overview]
Message-ID: <70bc64f6-3513-2924-9ba0-0e38e0e9d308@iee.email> (raw)
In-Reply-To: <8e7ff0b2-9f62-8ec6-5316-eb9cee25024e@syntevo.com>
On 27/11/2019 18:59, Alexandr Miloslavskiy wrote:
> 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.
Hmm, 45 minutes of cloning and rebuild, but finally it compiled clean
(both Release and Debug)
next prev parent reply other threads:[~2019-11-28 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 8:28 [PATCH 0/1] contrib/buildsystems: fix Visual Studio Debug configuration Alexandr Miloslavskiy via GitGitGadget
2019-09-23 8:28 ` [PATCH 1/1] " Alexandr Miloslavskiy via GitGitGadget
2019-09-24 14:17 ` Alexandr Miloslavskiy
2019-09-25 15:20 ` Johannes Schindelin
2019-11-27 17:56 ` Philip Oakley
2019-11-27 18:59 ` Alexandr Miloslavskiy
2019-11-27 21:42 ` Philip Oakley
2019-11-28 0:34 ` Philip Oakley [this message]
2019-11-28 10:07 ` Alexandr Miloslavskiy
2019-11-29 11:53 ` Philip Oakley
2019-11-29 13:19 ` Philip Oakley
2019-12-01 23:41 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70bc64f6-3513-2924-9ba0-0e38e0e9d308@iee.email \
--to=philipoakley@iee.email \
--cc=alexandr.miloslavskiy@syntevo.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).