Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[opencv4:x64-windows] build failure #7856

Closed
melhashash opened this issue Aug 23, 2019 · 2 comments · Fixed by #11130
Closed

[opencv4:x64-windows] build failure #7856

melhashash opened this issue Aug 23, 2019 · 2 comments · Fixed by #11130
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@melhashash
Copy link

Host Environment

  • OS: Windows 10
  • Compiler: C/C++ Optimizing Compiler Version 19.00.24215.1 for x64

To Reproduce
Steps to reproduce the behavior:
vcpkg.exe install opencv4[contrib,nonfree]:x64-windows

Failure logs
Package: opencv4:x64-windows
Vcpkg version: 2019.08.16-nohash

Additional context
ninja: build stopped: subcommand failed.
config-x64-windows-out.log
install-x64-windows-dbg-out.log

@melhashash melhashash added the category:port-bug The issue is with a library, which is something the port should already support label Aug 23, 2019
@cenit
Copy link
Contributor

cenit commented Aug 24, 2019

I never tried using VS2015 to build opencv 4.1.x and I don’t have any machine ready for that

@vicroms @Rastaban what about adding more configurations to the CI? Same triplets as of now, but different gcc versions on Linux, different clang versions on MacOS, and different msvc versions on Windows. We would highlight problems like this

@napester: I assume you can’t update to a newer version, am i right? If you can, please update to VS2017 or better to VS2019 and you should not receive any build error

@JackBoosY
Copy link
Contributor

@napester Thanks for reporting this issue.
Please install Windows SDK version above 10.0.17134.0 and then rebuild opencv4.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants