Makefile Tools installs statistics

<h1 align=center> <img align=center width=48 src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/makefile-logo-no-background.png" alt="Makefile Logo"/> Makefile Tools </h1> <p align=center ><i>Enhancing Makefile development in VS Code.</i></p> <div align=center> <img alt="VS Code" src="https://img.shields.io/badge/VSCode-7d57c2?style=for-the-badge&logo=visual%20studio%20code&logoColor=white"/> <img alt="Makefile" src="https://img.shields.io/badge/MAKEFILE-white?style=for-the-badge&color=7d57c2&cacheSeconds=3600"> <img alt="C" src="https://img.shields.io/badge/C-7d57c2?style=for-the-badge&logo=c&logoColor=white"/> <img alt="C++" src="https://img.shields.io/badge/C%2B%2B-7d57c2?style=for-the-badge&logo=c%2B%2B&logoColor=white"/> </div> <div align=center> <img alt="VS Code Marketplace Downloads" src="https://img.shields.io/visual-studio-marketplace/d/ms-vscode.makefile-tools?style=for-the-badge&color=064f8c&cacheSeconds=3600&link=https%3A%2F%2Fmarketplace.visualstudio.com%2Fitems%3FitemName%3Dms-vscode.makefile-tools"> <img alt="VS Code Marketplace Version" src="https://img.shields.io/visual-studio-marketplace/v/ms-vscode.makefile-tools?style=for-the-badge&color=be2128&cacheSeconds=3600&link=https%3A%2F%2Fmarketplace.visualstudio.com%2Fitems%2Fms-vscode.makefile-tools%2Fchangelog"> <img alt="Closed Issues" src="https://img.shields.io/github/issues-closed/microsoft/vscode-makefile-tools?style=for-the-badge&color=249847&cacheSeconds=3600&link=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode-makefile-tools%2Fissues"> </div> <br/> <img style="width: 100%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/makefile-tools-banner.png" alt="Makefile Tools Banner"/>

Introduction

Makefile Tools provides the native developer a full-featured, convenient, and powerful workflow for Makefile-based projects in Visual Studio Code. It enhances the development experience with pre and post-configuration script automation, allows for easy switching between multiple configurations, and supports rich IntelliSense features for Makefile. The customizable Project Outline view and environment variable management also simplifies the development experience. Additionally, it can generate a compilation database for integration with Clang tools and other editors/IDEs.

<details open> <summary> Features </summary><br/> <p align=center> <img width="49%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/built-in-makefile-language-services-feature.png" alt="Built-In Makefile Language Services"/> &nbsp; <img width="49%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/project-outline-feature.png" alt="Project Outline"/> </p> <p align=center> <img width="49%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/pre-and-post-configure-scripts-feature.png" alt="Pre & Post-Configure Scripts"/> &nbsp; <img width="49%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/multiple-configurations-feature.png" alt="Multiple Configurations"/> </p> <p align=center> <img width="49%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/environment-variable-configuration-feature.png" alt="Environment Variable Configuration"/> &nbsp; <img width="49%" src="https://github.com/Microsoft/vscode-makefile-tools/raw/HEAD/res/graphics/compile-commands-generation-feature.png" alt="Compile Commands Generation"/> </p> </details>

Getting Started

Activating the extension

The extension will activate when it finds a Makefile in your ${workspaceFolder}. If your Makefile does not reside in the root of your folder, use the makefile.makefilePath (which generates the make switch -f) or makefile.makeDirectory (which generates the make switch -C) settings to instruct the extension where to find it.

Pre-configuring your project

If you need any environment variables to be set or any terminal operations to be run before configure/build (like the usual ./autogen.sh, ./configure or vcvarsall.bat), you need to launch VSCode from a terminal that is already set up according to your project requirements OR you can point the makefile.preConfigureScript setting to a batch script file and invoke it at any time via the command makefile.preconfigure in the palette. By setting makefile.alwaysPreConfigure to true, you don't need to run the pre-configure command separately. The extension is going to invoke the script before every configure operation.

Configuring your project

By default, the extension will attempt to use a make program that resides within your $PATH to configure the project. If you use a different flavor of the make tool or if it is not in your $PATH, use the makefile.makePath setting to instruct the extension where to find it. Provide a file/command that is in the system path, prefixed with ${workspaceRoot}, or an absolute path as relative paths will not be resolved properly.

The extension can also avoid running the make program when it configures your project, if you point the makefile.buildLog setting to the output of a build.

Now, you are ready to configure your project. If you normally just run make in the terminal to configure/build your project, you shouldn't need to do anything else at this point besides accept the prompt from cpptools to allow this extension to configure IntelliSense:

If you don't see that message, or you accidentally dismissed it, you can grant Makefile Tools permission to configure IntelliSense by running the C/C++: Change Configuration Provider... command and selecting Makefile Tools from the list.…