Premake
Powerfully simple build configuration.
Become a contributor
Financial contributions
Patrons 🍻
Does your company use Premake? Ask your manager to support us! Your company logo will appear prom... Read more
Starts at
$500 USD / month
Top financial contributors
Individuals
Renaud Guillard
$20 USD since Nov 2019
Emilio Lopez
$15 USD since Feb 2020
Jason Perkins
$14 USD since Jun 2003
Wracky
$10 USD since Nov 2019
MiCroN3000
$10 USD since Dec 2019
Organizations
CitizenFX Collective
$6k USD since Aug 2019
Industrious One
$500 USD since Jul 2019
What's new with Premake
Stay up to dates with our latest activities and progress.
Community Update #3
Community Update #2
…more importantly, while I have this opportunity to log solid blocks of time to Premake (thank you!), I'm taking on its biggest weakness: the project configuration system, the heart of the program that stores your scripted project settings and serves them back to the exporters and actions. The shortcomings in this system are the reason why it's so difficult to support per-file configurations, why we struggle to express makefiles succinctly, and why we can't do a better job of scaling up to large numbers of platforms/architectures/toolsets/etc. Fixing this fixes many things.
To get this done in the most expedient way, and with the least disruption, I’ve spun up a new working space at premake-next. For those interested, you can read more about what I'm doing, why, and where it's all headed over there. And I’ll also continue posting regular updates here on the Collective.
Which brings me to the part where I give a huge THANK YOU! to our continuing sponsors CitizenFX Collective and Industrious One. I would not be able to tackle any of this were it not for your continued support. 🙌
For the next cycle, I plan to start filling in the details of an improved configuration storage approach and, if possible, merge another pull request or two.
~st.
Completed Tasks:
- Boostrapped Premake-next
- Closed PR #1259 with PR #1355
- Closed PR #1271 with PR #1356
- Closed PR #1063 with PR #1357
- Merged new PRs #1345, 1351, 1352, 1353, 1358
- Closed issue #38 and PR #624 with feature request #1344
- Closed issue #237 and PR #956 with feature request #1346
- Closed stale PRs #968, 1003, 1054, 1112, 1119, 1196, 1252, 1301
- Added new "Get help" and "Ask a question" issue templates; improved "Report a bug" and "Request a feature" templates
Community Update #1
As I'm sure you are all too aware, Premake development has slowed to a trickle. I've been taking on more and more client work to keep the books balanced, and there simply isn't any useful time left over at the end of the day. A not uncommon problem!
So I'm trying an experiment: can we, as a community, create a pool of funding to speed up Premake's development? Is there enough interest to make it happen? If so, I would be delighted to transition hours from client work back to Premake, as well as put funds toward bounties and recognizing contributions from the community.
The experiment is now officially underway. As long as it continues, I'll provide regular updates on our progress and upcoming work. This cycle, I was able to…
- Set up this OpenCollective, enabling the Premake project to accept contributions to fund on-going development and community support (#1314, #1316)
- Register @premakeapp on Twitter for announcements and group communication (and maybe a little self-promotion). Come join us! (#1315)
- Improve the project on-boarding experience with a new README.md and CONTRIBUTING.md (#1324, #1325)
- Improve the collaboration process with new issue, feature, and pull request templates (#1326, #1327)
I'm not charging any expenses against the collective this cycle so we can build up a balance to recognize cool or important contributions from the community. You can track our finances and transactions at any time on our OpenCollective page.
For the next cycle, I'd like to show a little maintainer love by working down (and ideally clearing) the open pull request queue and, time permitting, do a bit of grooming on the open issue list as well. Longer term, I've put a great deal of time and thought into fixing Premake's core configuration engine, which is holding back development on a number of important features. I've figured out how it should work; now I'm puzzling over how to get there from where we are.
Many thanks to CitizenFX Collective and Industrious One for their generous support this cycle. Your contributions make this possible! 🎉
~st.
(Your feedback is welcome and appreciated—come find us at github.com/premake or @premakeapp.)
Budget
See how money openly circulates through Premake. All contributions and all expenses are published in our transparent public ledger. Learn who is donating, how much, where is that money going, submit expenses, get reimbursed and more!
Monthly financial contribution to Premake (Sponsor)
Today’s balance
$4,413.50 USD
~ $13,537.58 USD
Premake is all of us
Our contributors 10
Everyone who has supported Premake. Individuals and organizations that believe in –and take ownership of– our purpose.
Emilio Lopez
Total contributions
$15 USD
Adding a contribution to get Premake going :)
About
Premake is a command line utility which reads a scripted definition of a software project, then uses it to perform build configuration tasks or generate project files for toolsets like Visual Studio, Xcode, and GNU Make. Premake's scripts are little Lua programs, so the sky's the limit!
By supporting our OpenCollective, you help Premake's core maintainers spend more time supporting the community and developing new features for everyone. If you use Premake at work, your company can contribute as well: OpenCollective provides invoices and reports to make it easy, and all expenses are public so you can see where the money is going. Learn more at Become a Sponsor.