Joris Dauphin

Should it be an external [modules](https://premake.github.io/community/modules/) instead?

According to https://docs.microsoft.com/en-gb/cpp/build/reference/compiling-a-c-cpp-program?view=msvc-170 > Compiler options are processed "left to right," and when a conflict is detected, the last (rightmost) option wins. So `"/OPT:NOREF"` `"/OPT:NOICF"` should take precedence. So only...

With option1, it is easy to use extra premake modules. Not sure how to do it with option2.

@eariassoto: How do you (plan to) handle extra [modules](https://premake.github.io/community/modules/)? (That doesn't fit my needs anyway as I run premake in a script (multiple projects)).

So https://github.com/Enhex/premake-vscode might help.

[`propertydefinition`](https://premake.github.io/docs/propertydefinition/) might help, something along: ``` propertydefinition { name = "ShaderOptimizationLevel", display = "Shader Optimization Level", value = false, switch = "/Od"} ``` And ``` buildcommand "vendor/shader-compiling/fxc.exe [ShaderOptimizationLevel] .." ```...

> [ FAILED ] premake_http.https_get_verify_peer > HTTP response code said error > The requested URL returned error: 504 Gateway Time-out Unrelated to my changes. :-) Not the first time that...

On my side, for testing purpose, I created https://github.com/Jarod42/premake-sample-projects So there are samples for some features as a whole.

You might need to clean build directory (remove intellisense Database) so it rebuild its database.

I added gmake2 action too, same error. I didn't create vs github action yet. single/double quotes are interpreted by shell, so `-D'COMPLEX_MACRO=void f() {}'` should be the same as `-DCOMPLEX_MACRO="void...