If for some reason the user input field doesn't show up, you may have to click the "Add configuration" button in the section above. Mine were in /usr/bin/clang and /usr/bin/gcc. Then type the path into the "Compiler Path" field. Every linux system will generally ship with a C compiler, so you can search for yours via google, or in the terminal try the which command and the name of common compilers: gcc, clang, llvm. Mine automatically detected the installed compilers and listed them in the dropdown, but if yours doesn't for some reason, you can always find the path and add it manually. In the window that opens, scroll down and click on "Compiler Path" dropdown. Once done, use Ctrl + Shift + P to open the command pallette, type in "c/c++" and choose 'edit configuration UI' from the list. Once you're comfortable with setting up the compiler, you can also create a separate workspace for each project folder instead of using the top level parent, if you prefer to organize it that way. Then save the workspace from the File menu, or, once you close the editor, you'll be prompted to save it. Once the folder is created, go to File>Add Workspace to Workspace. Another option would be to create a test folder to get comfortable with this setup, and then create your real project folders and set them up as their own workspaces, which will result in a more organized final setup. I'd recommend creating a top level parent folder to hold all your C projects and then use subfolders for each project (good if you're doing learning exercises). Once the C/C++ extension is installed, you'll need to create a workspace to set up and run compile tasks. I just started using it for JavaScript and it's great to be able to run and test your files right in the editor without having use a browser. I'd also recommend installing Code Runner as well - it's not as flexible as the setup described below, but it's really handy for lots of other languages. First, if you haven't yet, install the C/C++ extension that is available from Microsoft.Īlso note that, since Macs use a *nix OS, most of this can be applied to setting up on a mac as well, with the possible exception of some of the paths.
0 kommentar(er)
