git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] ci(vs-build): stop passing the iconv library location explicitly

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 4, 2020, 20:02 UTC
Message-ID
<xmqqv9dhe3wi.fsf@gitster.c.googlers.com>
In-Reply-To
<pull.805.git.1607091741254.gitgitgadget@gmail.com>

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com> writes:

Show 17 quoted lines
> From: Dennis Ameling <dennis@dennisameling.com>
>
> Something changed in `vcpkg` (which we use in our Visual C++ build to
> provide the dependencies such as libcurl) and our `vs-build` job started
> failing in CI. The reason is that we had a work-around in place to help
> CMake find iconv, and this work-around is neither needed nor does it
> work anymore.
>
> For the full discussion with the vcpkg project, see this comment:
> https://github.com/microsoft/vcpkg/issues/14780#issuecomment-735368280
>
> Signed-off-by: Dennis Ameling <dennis@dennisameling.com>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
>     ci: fix the vs-build job so that CI builds pass again
>     
>     This was noticed first in a Git for Windows PR.

This is probably the same breakage I've been seeing, e.g. https://github.com/git/git/runs/1494253517

Thanks for taking care of it.

I guess we should just apply directly to 'master' (or 'maint' and merge up), but I can queue it just like all other topics and have it traverse through 'seen'->'next'->'master'.

Previous: Johannes Schindelin via GitGitGadgetNext: Johannes Schindelin
Message 2 of 3 in “ci(vs-build): stop passing the iconv library location explicitly”
  1. ci(vs-build): stop passing the iconv library location explicitlyJohannes Schindelin via GitGitGadget, Dec 4, 2020
  2. Junio C HamanoDec 4, 2020
  3. Johannes SchindelinDec 4, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.