Add support for NMake project files
See original GitHub issueOur project currently defines the following nodes under the PropertyGroup
nodes:
NMakeBuildCommandLine
, NMakeReBuildCommandLine
, NMakeCleanCommandLine
, NMakeIncludeSearchPath
, NMakePreprocessorDefinitions
.
It seems like none of these are read (realistically, only the include path and preprocessor definitions are relevant) and passed on to clang-tidy
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
NMake Property Page (Windows C++)
The NMake property page lets you specify build settings for Makefile projects. (NMAKE is the Microsoft implementation of Make.).
Read more >A visual studio solution that does one nmake
1) Open the VC Command Prompt · 2) Run nmake on a .mak file · 3) That was it, your dll gets spit...
Read more >2.3 Building from the Command Line with nmake
When you build from Microsoft Visual Studio, Visual Studio invokes nmake against the product's .mak file as an external makefile, with a command...
Read more >Building with Make or Nmake
This document describes the process to build the software from source using Make or Nmake on Windows. First make sure you have read...
Read more >Building in Visual Studio Code with a Makefile - Earthly Blog
To compile and link the project, you can add a Makefile to the root of the project folder. It will be detected automatically...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi,
Thank your for your suggestion 👍 We’ll look into it.
Hi,
I am on vacation from work where the projects live, but based on your output, it looks like these are being read now (possibly due to changes since the construction of the issue?). I think it is fine to close this issue for now and I’ll re-open it if the problem is still present when I can check in a few weeks.