You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using tools.vswhere() in validate() function of a recipe raises a ConanException: Cannot locate vswhere in 'Program Files'/'Program Files (x86)' directory nor in PATH when run by CCI CI/CD.
There is no problem when recipe is created on my computer or windows docker images using MS build tools.
Could you investigate this bug? vswhere.exe should be located in C:\Program Files (x86)\Microsoft Visual Studio\Installer
Using vswhere in validate() function could be used to determine the exact version of Visual Studio (major and minor version numbers). This information can be important to know which new C++ features the compiler supports and to throw ConanInvalidConfiguration when not supported.
The text was updated successfully, but these errors were encountered:
This is not a bug. The validate() method will be executed in a Linux container before delegating the build to a Windows machine. If the validate() computes a ConanInvalidConfiguration then the build won't take place.
Let's move to the recipe and see how can we work on this issue for that use-case.
Using
tools.vswhere()
invalidate()
function of a recipe raises aConanException: Cannot locate vswhere in 'Program Files'/'Program Files (x86)' directory nor in PATH
when run by CCI CI/CD.This is a: use case.
There is no problem when recipe is created on my computer or windows docker images using MS build tools.
Could you investigate this bug?
vswhere.exe should be located in C:\Program Files (x86)\Microsoft Visual Studio\Installer
Using vswhere in validate() function could be used to determine the exact version of Visual Studio (major and minor version numbers). This information can be important to know which new C++ features the compiler supports and to throw ConanInvalidConfiguration when not supported.
The text was updated successfully, but these errors were encountered: