tag:help.appveyor.com,2012-11-13:/discussions/problems/27713-build-broken-without-any-change-vcpkg-not-foundAppVeyor: Discussion 2020-07-14T10:55:30Ztag:help.appveyor.com,2012-11-13:Comment/484507342020-07-08T14:42:59Z2020-07-08T14:44:20Zwindows build broken without any change [vcpkg not found]<div><p>I haven't build my project for 5 days and now every build fails even with the same changes of the latest working build</p>
<ul>
<li>[working] <a href="https://ci.appveyor.com/project/L4ZZA/pyro/builds/33864212">https://ci.appveyor.com/project/L4ZZA/pyro/builds/33864212</a></li>
<li>[not working] <a href="https://ci.appveyor.com/project/L4ZZA/pyro/builds/33978188">https://ci.appveyor.com/project/L4ZZA/pyro/builds/33978188</a></li>
</ul>
<p>It seems like something went wrong with vcpkg as the only project not building is my tests project as it doesn't find the boost library</p></div>L4ZZAtag:help.appveyor.com,2012-11-13:Comment/484507342020-07-08T18:04:39Z2020-07-08T18:04:39Zwindows build broken without any change [vcpkg not found]<div><p>There was VS 2019 image update on July 3 which, of course, bumped vcpkg: <a href="https://www.appveyor.com/updates/2020/07/03/">https://www.appveyor.com/updates/2020/07/03/</a></p>
<p>Try disabling vcpkg cache in your build.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/484507342020-07-09T08:16:01Z2020-07-09T08:30:42Zwindows build broken without any change [vcpkg not found]<div><p>I did and it still doesn't work.. the <em>VcpkgTripletSelection</em> defaults to <code>x64-windows</code> instead of using the one specified inside the project <code>x64-windows-static</code><br>
<a href="https://ci.appveyor.com/project/L4ZZA/pyro/builds/33986729">https://ci.appveyor.com/project/L4ZZA/pyro/builds/33986729</a></p>
<p>The workaround I found was to explicitly add vcpkg include dir <code>$(VcpkgInstalledDir)x64-windows-static/debug/include</code> to debug and <code>$(VcpkgInstalledDir)x64-windows-static/include</code> to release. Not ideal.<br>
<a href="https://ci.appveyor.com/project/L4ZZA/pyro/builds/33986703">https://ci.appveyor.com/project/L4ZZA/pyro/builds/33986703</a></p></div>L4ZZAtag:help.appveyor.com,2012-11-13:Comment/484507342020-07-09T08:35:36Z2020-07-09T09:58:33Zwindows build broken without any change [vcpkg not found]<div><p>I also tried to use <code>image: Previous Visual Studio 2019</code> and it works without hardcoding the additional includes <a href="https://ci.appveyor.com/project/L4ZZA/pyro/builds/33997468">here</a>.<br>
Is it possible that this has to do with the most recent <a href="https://github.com/microsoft/vcpkg/releases/tag/2020.06">vcpkg release</a>?<br>
It's pretty weird that it still works on my machine after updating vpkg..</p></div>L4ZZAtag:help.appveyor.com,2012-11-13:Comment/484507342020-07-13T08:58:55Z2020-07-13T08:58:55Zwindows build broken without any change [vcpkg not found]<div><p>any update on this? :)</p></div>L4ZZAtag:help.appveyor.com,2012-11-13:Comment/484507342020-07-13T22:33:14Z2020-07-13T22:33:14Zwindows build broken without any change [vcpkg not found]<div><p>Honestly, I'm not an expert in C++/vcpkg, but perhaps vcpkg team could help if you submit an issue there.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/484507342020-07-14T10:55:28Z2020-07-14T10:55:28Zwindows build broken without any change [vcpkg not found]<div><p>well, the problem is not with vcpkg in general, but with the image update.</p>
<p>Vcpkg works on my machine as expected, even after updating to its latest released version 2020.06.</p>
<p>On AppVeyor though, the build fails using <code>Visual Studio 2019</code>, but succeeds using <code>Previous Visual Studio 2019</code> without changing anything else in the yaml file and this ever since the latest image update.</p>
<p>I can honestly only see a problem that has to do with the OS image here.</p></div>L4ZZA