Community Update #10
Premake 5.0-beta1! 🥳​
After one of the world's longest alpha cycles, Premake5 has finally entered beta! I don't know about you, but I definitely had a drink to celebrate. Might have been two, even. Probably.
As previously discussed, we've started the process of stabilizing 5.0 and shifting breaking changes over to the new v6.x branch. We've set up a milestone to track our progress toward a stable 5.0 release, and this is the first step in working it down.
Most of the changes in the queue are under-the-hood: release automation, bootstrapping, and unit test fixes. The only potentially significant breaking change remaining is promoting the gmake2
exporter, which I will be prioritizing for the next beta. If you happen to still be using the older gmake
exporter, please give gmake2
a try and let us know if you encounter issues! Most fixes have been going to gmake2
lately, so we expect your experience will be a good one.
{/* truncate */}
Premake6​
As of this morning, Premake6 is now "self-hosting" on Visual Studio, Make, and Xcode, meaning that it can generate its own project files, which can then be used to build Premake6. This is a big milestone, since we can now move past isolated unit tests and actually verify our changes with working builds on all three toolsets. All of Premake's core functionality is now fully online, and we're shifting our focus to prioritizing and porting individual features. Still lots of hardcoded settings and to-dos, but full speed ahead!
(Speaking of which: I know the pace is slow—definitely slower than I would like—but thanks to our backers it’s steady progress. For a bunch of nights-and-weekends part-timers we’re doing alright.)
I'm currently taking a bug fix & cleanup pass over what we have so far, and filling in gaps in the documentation to make sure we're not leaving too much debt behind. High priority next steps include rethinking how we abstract toolsets like GCC & Clang, so we can push ahead implementing new features on top of those abstractions. And then implementing links and (...drum roll...) usages (yes, really!) so we can start linking projects and their dependencies together.
Hat tip to @nickclark2016 for tackling the new makefile exporter!
Community Contributions​
Yay open source development! 🎉 Big shout out to everyone who took the time to contribute this cycle.
- #1629 Add support for macOS universal binary (@tempura-sukiyaki)
- #1661 Add
frameworkdirs
support to gmake & gmake2 with gcc/clang toolsets (@depinxi) - #1672 C# Symbol Premake → VS Mapping Changes (@nickclark2016)
- #1680 Fix some build issues with mingw (@Biswa96)
- #1687 Update deprecated entry for newaction (@Jarod42)
- #1704 VS2022 Exporter (@nickclark2016)
- #1710 Add support for SSE 4.2 (@ActuallyaDeviloper)
- #1712 Add OpenMP support for Visual Studio (@T-rvw)
- #1713 Upgrade docusaurus version to beta.6 (@KyrietS)
- #1715 Docs maintenance (@KyrietS)
- #1718 Deprecate
configuration()
(@starkos) - #1720 Improve
justmycode
(@T-rvw) - #1721 Add custom rules for Gmake2 & Codelite (@Jarod42)
- #1723 Add configuration condition to VS csproj references ItemGroup (@cicanci)
- #1726 Updated cdialect and cppdialect docs (@LORgames)
- #1727 Updated architecture docs (@LORgames)
- #1728 Add action to check for and generate missing documentation (@LORgames)
- #1730 Added missing
compileas
values to docs (@LORgames) - #1734 Add VS 2022 bootstrapping support (@afxw)
- #1736 Update showcase to include Orx (@sausagejohnson)
- #1737 Change Visual Studio Version to 17 so sln is opened with VS2022 (@simco50)
- #1739 Fix #1628 failing macOS os.findlib() test (@starkos)
- #1744 Add check for missing values in documentation (@LORgames)
- #1745 Adding documentation for module options (@hannes-harnisch)
- #1749 Changed C++20 to emit C++20 instead of C++Latest in MSVC (@nickclark2016)
- #1752 Added C17/GNU17 support to gmake/gmake2 exporters (@nickclark2016)
- #1753 Update documentation link in README (@nickclark2016)
Extra thanks to the unsung heroes not mentioned here who helped review pull requests, triage issues, and generally keep the machine humming.
Our Sponsors​
Which brings us at last to our regular thank you & shout out to our premier sponsor Cfx.re as well as all our monthly backers—be sure to check out their work and support them back if you can!
I welcome questions, suggestions, and concerns. Message or DM me at @premakeapp, email at starkos@industriousone.com, or open a discussion on GitHub.