Skip to content
Discussion options

You must be logged in to vote

An assembly language requirement in the top-level CMake project triggered this. We have no assembly requirement at the top level, so removing this also eliminates the policy warning.

In subprojects, if the project requires it, there is always at least one assembler configured that isn't cl.exe, and thus the policy doesn't trigger a warning there.

PR: #1384

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by JanFellner
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants