![]() We have also released a command that will build and debug the active code file which should enable the "proof of concept" scenario you mentioned (single code file with int main and other experimental code). If this isn't working for you, we'd like to know about it. When opening a new folder that has not been configured we will scan for installed compilers and auto-populate this if it finds a Visual Studio installation. Since your original post, the extension has added a "compilerPath" property to our config schema which removes the need to manually paste in system include paths. The C++ extension is capable of detecting the Visual Studio Build tools and using them to configure your c_cpp_properties.json automatically. Thank you folks for all your maybe you can help me understand better what you would like to see that is not present in the extension today. Too bad I don't know any electron or JS programming. If this was in C I would have written a code for a directory traversal. Build standard templates based on its finding, both for C and C++ projects. All compiler and build directories created on its own. Here is what is expected from VS Code in Windows: An automated scan for standard directories as soon as VS Code is fired / or C environment is setup for the first time. Unless I manually go and tweak each one of my programs. The version /2019 gets appended and in the end it renders my code useless. But of-course it is too much to expect.Įven now as Build Tools for Visual Studio 2019 RC is making its release. Proof of concepts etc, who don't need project management. Which is VS Code (which has an integrated debugger) will work with Visual Studio Build Tools on Windows environment.īasically this would have been an epic solution for standard 300-400 line C programs. I have given up on having an idea that a lightweight solution. OS : Latest Windows 10 and latest Visual Studio Code with up to date extension ms-vscode.cpptools 0.16.1.Īs an original poster of this thread. This is somewhat unrealistic that include folder is inside version 8, which would mean in case of change in version number would leave the code pretty much useless. "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/MSBuild/15.0/Bin" "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/", "C:/Program Files (x86)/Windows Kits/10/Include/0.0/ucrt" "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/8/include", "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/*",
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |