Nick Clark
Nick Clark
I don't have an answer for you, as I'm not terribly familiar with vpaths in Premake (hence why I didn't answer).
Looking further into your described behavior, this may be a bug.
We have made no efforts to build console modules. It's enough of a legal headache, and we have had higher priority things pop up. If specific console vendors reach out,...
Correct, we should either adjust the documentation or adjust the behavior of `--os` and `_TARGET_OS`. I would recommend using `target.os()` for now.
Just for awareness, @Jarod42 has a nice CI action to get premake set up: https://github.com/marketplace/actions/install-premake5
I cannot reproduce this using the suggested action above (Jarod42/install-premake5), nor can I reproduce this locally. This may be a runner issue.
Just poking on this to resolve the conflicts
To keep parity in support between C# and C++ projects, would you mind adding support there and adding the corresponding unit tests?
I'm not 100% sure that C++ has the problem, but I'd expect the same behavior (allowing per config steps).
We don't have this functionality built directly in Premake, but you should be able to use something like: ```lua filter "files:ABC.c" buildoptions { "/Za" } filter "" ```