Joris Dauphin

Is project location at the same place than premake5.lua? (else path in `filter "files:assets/**.ico"` should be fixed). Just did a quick test, and in visual, property of the ico file...

> Nevermind. It may be marked as ResourceCompile, but there are still no resource.h, Engine.rc, or Engine.aps files. Project with resource I work on doesn't use `buildaction "ResourceCompile"` for the...

> This PR lets users to write custom rules compatible with [msbuild batching](https://learn.microsoft.com/en-us/visualstudio/msbuild/msbuild-batching?view=vs-2022). By providing @(Rule) as input and @(Rule->'%(Output)') as output, msbuild can recognize this task can be batched...

OK, so your code is a shorthand for: ```lua rule "myrule" --location(LocationDir) --display "My custom rule" fileextension ".txt" -- propertydefinition { .. } -- buildinputs { "%{file.relpath}.in" } -- Possible...

Also apply to gmake. As I see, `group` adds rules in makefile to build all projects of the group. I haven't expected group to appear in Makefile, but ok...

As it is an issue only with gmake/gmake2, so check should be done in gmake/gmake2, IMO.

I think example expected to be: ``` workspace "MyWorkspace" configurations { "Debug", "Release" } platforms { "Windows", "Unix", "Mac" } filter "platforms:Windows" system "windows" filter "platforms:Unix" system "linux" filter "platforms:Mac"...

Remember you can generate solution for other platform/system/os/architecture. So with this exemple, you might generate a unique solution usable on all 3 systems (when using appropriate configuration/platforms). doc should mention...

I would say default is current system normally (Not sure if **action** does/might override that). I have personally never used `"system"`. (And I build on ubuntu/macosx/windows).

I think that doc page should focus on `system` meaning, not on filtering.