![]() ![]() ![]() Select cl.exe build and debug active file in it. Press F5 or Ctrl + F5 and the editor will prompt a dropdown menu. That’s all due to a strange bug making the editor always to consider C:/Program a command. ![]() There is a bit difference between my sample and the offical example of running VS Code outside the Developer Command Prompt: the second argument of is no longer a full path. Then return to your C source file, press Ctrl + Shift + B, and the program will be compiled. Then in the pop-up window click New to add this value: In the settings window, select Path and then click Edit…. Search path in the search box in your task bar and open Edit environment variables for your account. ![]() The configuration of environment variables comes first. The actual approach to configure Windows C++ (MSVC) In the first few steps, the tutorial gives us the correct guidance, until step Build helloworld.cpp. Here I’m presenting the detailed configuration procedure with Visual Studio 2019 (or the toolset of Visual Studio 2019). So did I.įortunately, after struggling with the editor and the compiler for a whole morning, I ultimately grasp the key to make it. In fact, Microsoft has already given us an official tutorial on how to use Windows C++ in Visual Studio Code, yet if following it, you are bound to a fatal error. In this blog, I’m going to introduce how to configure VSCode for an easy compiling and debugging process. But how to simplify it? I know you would say Visual Studio Code. However, for just a single file C program, Visual Studio resembles a steam engine used to crack nuts, not only wasting so many advanced features of it but also making the precedure much more complicated. Recently I’m attending my college’s Computer Language and Programming Lesson, in which Visual Studio is required to use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |