Joris Dauphin

Didn't test those repositories, but those are modules to use to extends premake with extra support. Those are not listed in https://premake.github.io/community/modules/ :-/ To use modules, see https://premake.github.io/docs/Using-Modules/

d support would probably disappears "soon", only supported by one deprecated generator (gmake). > why not to detect it like [..] ? Resources are limited... :-/

> On the matter of adding to the community modules, I do not know what the threshold for usefulness is, before modules are added to that page, otherwise I would...

That option is clang specific (I don't know if it requires special handling for "msvc-clang" though), so: ``` filter {"toolset:clang*"} buildoptions "-stdlib=libc++" linkoptions "-stdlib=libc++" filter {} -- reset filter ```

`premake5 --help` lists that option (but it doesn't list that you might add toolset version as available value so `--cc=clang-14` should work too (with recent version of premake)).

> As an aside, there is no mention of the .pb.cc files that get generated anywhere Some generators (as gmake* ) only considers first `buildoutputs` in its rules. I suggest...

> then pick a single proto file I uses similar thing for a n-inputs 1-output rule.

Question has been asked/copied to https://stackoverflow.com/questions/77490364/premake-build-command-with-multiple-inputs-and-multiple-outputs

Tokens cannot be used in filter. So use: ``` filter "files:assets/**.ico" buildaction "ResourceCompile" ```

Which generator do you use? I bet than `buildaction "ResourceCompile"` is only supported by vs* action.