A quick update this cycle so I can get right back to it: I managed to free up meaningful blocks of time for Premake in February—felt good!—and tackle files and removeFiles, support configuration and platform specific files, and get it all exporting to Visual Studio (…and bulldoze through the rabbit holes along the way). From the user-facing side not a big change, but a hefty commit just the same.The core platform is starting to feel reasonably complete.

What's Next

1. For real this time, first thing: step away from the code and open an RFC on merging the projects. I've never been great at that whole "stepping away from the code" thing but I'll do my very best.
2. Work with @Kyriet to bring a new & improved documentation system online

Longer term: push to get the new code to the point where it can generate its own Visual Studio project files. I've actually done a good chunk of work on this, but wasn't quite able to bring it home this month. Then do the same with Xcode.

Meanwhile in V5

The community making the world a better place…

• #1551 Add NetCore to CLR API (@nickclark2016)
• #1554 [clang] Use `llvm-ar` linker when LTO flag is set (@JoelLinn)
• #1552 Fix MSC LTO, runtime, subsystem (@JoelLinn)
• #1560 Add newer shader versions (@dpeter99)
• #1562 Remove moduledownloader to avoid RCE (@gibbed)
• #1564 Improve .NET version check to support net5.0+ (@ClxS)
• #1565 Move AllowUnsafeBlocks to project level property (@ClxS)
• #1566 Set execute bit on Bootstrap.bat (@ratzlaff)
• #1571 Add useFullPaths for Visual Studio projects (@cos-public)
• #1576 Mesh and amplification shader type for Visual Studio (@pkurth)

Thanks!

Kudos and a call out to @samsinsane and the contributors listed above, CitizenFX Collective for their continued strong financial support, and to all of our monthly backers! Be sure to check out their work and support them back if you can!

Lots of big changes happening—I welcome questions, suggestions, and concerns. Everything is up for discussion, from the feature set to the coding style. You can message or DM me at @premakeapp, email at [email protected], or open an issue on the premake-next GitHub project.