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

'cl.exe' is not recognized as an internal or external command #33

Closed
kochol opened this issue May 11, 2020 · 3 comments
Closed

'cl.exe' is not recognized as an internal or external command #33

kochol opened this issue May 11, 2020 · 3 comments

Comments

@kochol
Copy link

kochol commented May 11, 2020

Hi I'm sure I set /ZI (not /Zi) compile flag but I get cl.exe error with vs 2019.

@crosire
Copy link
Owner

crosire commented May 16, 2020

You need to run blink from the VS command-line or have cl.exe (the C++ compiler) in your PATH.

@crosire crosire closed this as completed May 16, 2020
@kochol
Copy link
Author

kochol commented May 17, 2020

image
Same error and the cl is in path.

@crosire
Copy link
Owner

crosire commented May 17, 2020

Right, sorry, that should have been: You need to run the target application from the VS command-line (or use VC++ 2017, which does not suffer from this problem, or hardcode the path as per #31 (comment)). It's the same problem as noted in multiple issues: the original compile command-line is no longer written by VC++ 2019, so blink has to fall back to a custom one.

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