Closed IanLilleyT closed 4 years ago
By the way, my workaround is
require "vstudio"
premake.override(premake.vstudio.vc2010.elements, "nmakeProperties", function(oldfn, cfg)
return table.join(oldfn(cfg), { function(cfg)
premake.vstudio.vc2010.element("AdditionalOptions", nil, "/std:c++17")
end })
end)
I'd say it should be done in the same way as with the vcxproj generation.
I brought this up in a different issue: #670 but not sure if anyone saw.
Basically, I want intellisense to know the cpp dialect of my code in a VS makefile project. It seems like the best place to tell it that is under Project Properties -> NMake -> Additional Options. I don't know which solution is better: doing it through
cppdialect
or more manually throughbuildoptions
, but support for either would be cool.