Joris Dauphin

There is (pending) https://github.com/premake/premake-core/pull/2028 which add `idirafter`. Not checked clang documentation, but when adding test for that PR in my testing repo, I wrote that [doc](https://github.com/Jarod42/premake-sample-projects/tree/includedirsafter_test/projects/project-includedirsafter). And so that PR...

You want generation progress or build progress? For the former, it is related to premake and currently it just shows generated (project/solution) files. For the later, it would be part...

Probably documentation should be updated... Visual doesn't handle all gnu++XX and "non finished" version (C++0x, C++1y, C++1z, C++2a) (and ignore them, so default is used). C++20 would be better to...

@nickclark2016: It is there [modules/vstudio/vs2010_vcxproj.lua#L1634](https://github.com/premake/premake-core/blob/master/modules/vstudio/vs2010_vcxproj.lua#L1634). Ideally, I think exporters should warn about unsupported fields. (pretty sure we will disagree on that ;-) ) At minima, documentation should be updated.

Indeed, I miss `m.languageStandard`, so just doc to update, and warning later when supported. (A simple print would seem enough for me).

yes. that [page](https://premake.github.io/docs/cppdialect/)

There are still some [MACROs](https://en.cppreference.com/w/cpp/feature_test#Library_features) to know if feature is officially supported (and [`__has_include`](https://en.cppreference.com/w/cpp/preprocessor/include) too)...

https://github.com/kallisti5/guisan/pull/23 (with its [fix](https://github.com/kallisti5/guisan/pull/28)) fixes caps lock, and characters accessible with shift/alt-gr (as the one from 0-9)

Created https://github.com/premake/premake-core/pull/2047 which fixes gmake2

The single quote in message (`"Xxx'ing file"`) is problematic with some (versions of some) tools. "old" cmake version has that issue. premake-cmake fixed. codeblocks cannot be fixed Remain gmake2 and...