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

Re: [PATCH 1/1] contrib/buildsystems: fix Visual Studio Debug configuration

From
Philip Oakley <philipoakley@iee.email>
Date
Nov 29, 2019, 13:19 UTC
Message-ID
<9c5157df-adb0-0a84-2ff2-852ad7536874@iee.email>
In-Reply-To
<365668d0-ebb8-6b5c-99bd-29f0c8cec132@iee.email>
On 29/11/2019 11:53, Philip Oakley wrote:
Show 18 quoted lines
> On 28/11/2019 10:07, Alexandr Miloslavskiy wrote:
>> On 28.11.2019 1:34, Philip Oakley wrote:
>>
>>> Hmm, 45 minutes of cloning and rebuild, but finally it compiled 
>>> clean (both Release and Debug)
>>
>> I understand that the issue is resolved now.
>>
>> Probably your old repo was missing the libraries for whatever reason 
>> (like antivirus deleting them, etc), but build script thought that 
>> dependencies are properly built, so didn't attempt to rebuild them.
> I think I'll report that as an issue to the 
> https://github.com/microsoft/vcpkg folks so that there's better 
> detection for 'out of date' / updated vcpkg issues.
>
> The vcpkg_install.bat in /compat/vcbuild may need updating to do a 
> 'pull' if there is an existing directory. At the moment it's a rather 
> simplistic 'all or nothing' for getting all those extra packages.

Issue submitted as https://github.com/microsoft/vcpkg/issues/9148 -- Philip

Previous: Philip OakleyNext: Philip Oakley
Message 11 of 12 in “contrib/buildsystems: fix Visual Studio Debug configuration”
  1. 0/1 contrib/buildsystems: fix Visual Studio Debug configurationAlexandr Miloslavskiy via GitGitGadget, Sep 23, 2019
  2. 1/1 contrib/buildsystems: fix Visual Studio Debug configurationAlexandr Miloslavskiy via GitGitGadget, Sep 23, 2019
  3. Alexandr MiloslavskiySep 24, 2019
  4. Johannes SchindelinSep 25, 2019
  5. Philip OakleyNov 27, 2019
  6. Alexandr MiloslavskiyNov 27, 2019
  7. Philip OakleyNov 27, 2019
  8. Philip OakleyNov 28, 2019
  9. Alexandr MiloslavskiyNov 28, 2019
  10. Philip OakleyNov 29, 2019
  11. Philip OakleyNov 29, 2019
  12. Philip OakleyDec 1, 2019

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.