-- Installing: D:/packages/libvpx_x64-windows/lib/vpxmd.lib
CMake Error at ports/libvpx/portfile.cmake:104 (file):
  file INSTALL cannot find
  "D:/buildtrees/libvpx/x64-windows/x64/Release/vpxmd.pdb": File exists.
Call Stack (most recent call first):
  scripts/ports.cmake:142 (include)

Can you double confirm your changes?

-- Installing: D:/packages/libvpx_x64-windows/lib/vpxmd.lib
CMake Error at ports/libvpx/portfile.cmake:104 (file):
  file INSTALL cannot find
  "D:/buildtrees/libvpx/x64-windows/x64/Release/vpxmd.pdb": File exists.
Call Stack (most recent call first):
  scripts/ports.cmake:142 (include)

Can you double confirm your changes?

Is it from your pc?
On one of the computer libvpx compile without the change. I compile only the libvpx
Other computer I need to do the change. I compile libvpx as part of ffmpeg[all-gpl]
Maybe if I compile libvpx part of other libs, it happen?
Can you investigate it more?

Both computers running windows 10.

@talregev From our pipeline test, Windows10 with Visual Studio 2019.
I'll take a look at this.

@talregev What triplet do you use?

both x86-windows x64-windows

I haven't seen this happen on my CI (with x64-windows, x64-windows-static, and x64-windows-static-md); installation and compilation works fine. For the record, logs are here (for an ffmpeg master build, but otherwise the portfiles are the same, and in particular its the same for libvpx):

https://ci.appveyor.com/project/mcmtroffaes/ffmpeg-msvc-build/build/job/3yn0l4c3ge9fwkiy (x64-windows)
https://ci.appveyor.com/project/mcmtroffaes/ffmpeg-msvc-build/build/job/stavyb3m9i23my7w (x64-windows-static)
https://ci.appveyor.com/project/mcmtroffaes/ffmpeg-msvc-build/build/job/yr0nuflv8k8e4j0a (x64-windows-static-md)

This seems vaguely related to #12706 where the names were fixed to ensure the pdb files were found when compiling other apps against ffmpeg: the pdb files cannot be renamed after install.

This seems vaguely related to #12706 where the names were fixed to ensure the pdb files were found when compiling other apps against ffmpeg: the pdb files cannot be renamed after install.

I think it a good lead and I would start from there. Did you / ci try to compile vcpkg ffmpeg[all-gpl]?
I think when it compile ffmep with all the options, it also compile an apps that using ffmpeg, and maybe that why it rename the pdb. if it that the case, my suggestion is that the pdb always need to be rename

I think CRT linkage affected it.
Can you please provide vpx.vcxproj in VCPKG_ROOT/buildtrees/libvpx/x86-windows ?
And please provide the configure log.

Did you try / ci compile vcpkg ffmpeg[all-gpl]?

That's a good suggestion. I just tested vcpkg ffmpeg[core,ffmpeg,libvpx] on x64-windows and I can confirm that this works as expected at least on my local setup, with the ffmpeg binary able to encode with the libvpx-vp9 codec. Note that building ffmpeg (with whichever feature set) will not change the libvpx build on vcpkg: the ffmpeg build process does not influence the build process of its dependencies (such as libvpx).

@JackBoosY
I reproduce the problem with small example.
vcpkg install ffmpeg[core,ffmpeg,vpx]:x64-windows
vpx.vcxproj and logs.zip

Maybe the problem is from the things I install on visual studio. like mfc and clang support?

@JackBoosY any news?
Do you need more information?

@talregev Nope.

@talregev Can you test whether my changes is correct?

Thanks @JackBoosY! For the record, I've just tested this pr by compiling an application against ffmpeg[core,avcodec,vpx] on the x64-windows and x64-windows-static triplets, and I can confirm that it works like charm, besides also cleaning things up for libvpx detection on ffmpeg. Fingers crossed it also fixes @talregev 's issue.

LGTM! Thanks @talregev

Unfortunately it doesn't look like this fixed it, in #17331 with this change applied we still see:

CMake Error at ports/libvpx/portfile.cmake:104 (file):
  file INSTALL cannot find
  "D:/buildtrees/libvpx/arm-uwp/ARM/Release/vpx/vpx.pdb": File exists.

I think I have a fix, will put into the VM update PR

A user of my project is reporting this same failure even after this PR.

Edit: a manual cherry-pick of 91542464a564bfad42fcf2fa2fbafa3cab929a54 seems to have fixed it

I've started hitting this now as well on appveyor CI (not locally); 9154246 also fixed it for me. Perhaps something to do with the version of Visual Studio.

This issue is now being tripped on GitHub Actions CI. Is there any chance the fix can be fast-tracked @BillyONeal?

This issue is now being tripped on GitHub Actions CI. Is there any chance the fix can be fast-tracked @BillyONeal?

The VM update just landed, try again?

That seems to have fixed it, thanks!

@Hoikas @mcmtroffaes Fixed.

Yup, happy to confirm the fix in master now. Thanks a bunch!