If you regularly pass additional arguments to make, use the Makefile Tools’ Configurations setting ( nfigurations in settings.json) to specify those arguments. Now you’re ready to configure your project! If you normally run make from the command line without passing it any additional arguments, you shouldn’t need to do anything else at this point. If you don’t see that notification, or you accidentally dismissed it, you can grant Makefile Tools permission to configure IntelliSense by running “ C/C++: Change Configuration Provider” from the Command Palette and selecting Makefile Tools. Once your make path is properly set, accept the prompt to allow Makefile Tools to configure IntelliSense.

The Make Path setting tells the extension where to find your make executable. If your make.exe is not in your $PATH, update the Make Path setting by going to File > Preferences > Settings and then selecting makefile under Extensions. Configuring your projectīy default, the extension will attempt to use a make program that resides within your $PATH to configure the project. Update Makefile Path by going to File > Preferences > Settings and then selecting makefile under Extensions.Īfter updating Makefile Path, type “makefile” into the Command Palette and run a Makefile Tools command to activate the extension. If your project’s Makefile is not in the root folder, you can use the Makefile Path setting to instruct the extension where to find it.

Once the extension is installed, it will activate when it finds a Makefile in your project’s root folder. Give it a try and let us know what you think! Installing the extensionįirst, install the Makefile Tools extension from the VS Code Marketplace. We are excited to announce a brand-new extension for building and debugging Makefile projects in Visual Studio Code: Makefile Tools (preview)! The extension is in pilot stages, but we’ve curated a list of over 70 popular opensource Makefile projects that work with Makefile Tools.

C++ visual studio code mac