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

Build on Windows10 with VS2017 fails #54

Open
StefanRickli opened this issue May 20, 2019 · 2 comments
Open

Build on Windows10 with VS2017 fails #54

StefanRickli opened this issue May 20, 2019 · 2 comments

Comments

@StefanRickli
Copy link

StefanRickli commented May 20, 2019

I'm running VS2017 on Windows 10.

Here the build using nmake bin fails.

The following console output is from within the "x64 Native Tools Command Prompt for VS 2017":

C:\temp\cv2pdb>nmake bin

Microsoft (R) Program Maintenance Utility, Version 14.16.27027.1
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

        if     exist "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\\Common7\IDE\VCExpress.exe" "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\\Common7\IDE\VCExpress.exe" /Build Release src\cv2pdb.sln
        if not exist "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\\Common7\IDE\VCExpress.exe" "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\\Common7\IDE\devenv.exe" /Build Release src\cv2pdb.sln
NMAKE : fatal error U1077: "if": Rückgabe-Code "0x1"
Stop.

Running devenv /Build Release src\cv2pdb.sln directly stops as well because the solution needs an upgrade.

Workaround:

  • Run devenv src\cv2pdb.sln
  • Accept all "Unidirectional Upgrades"
  • Select cv2pdb in the Project Explorer
  • Go to Project Properties
  • Change "Windows SDK Version" to 10.xxxx using the dropdown arrow
  • Accept
  • Right click cv2pdb in the Project Explorer, select build
@rainers
Copy link
Owner

rainers commented May 21, 2019

You should use cv2pdb_vs12.sln. cv2pdb.sln is for VS2008. The makefile contains target cv2pdb_exe that uses the newer solution.

I guess I should remove the ancient cruft.

@StefanRickli
Copy link
Author

I guess I should remove the ancient cruft.

Or just hint to the new target in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants