Deleted the module I was using :(
Oh man, this is annoying! https://github.com/premake/premake-core/commit/74e689f651e3f31c0f3d6694649dcb60df4a68ae
I was using that! It would have been nice if someone asked me to update it rather than delete it all... this is quite hard to revert since there's a lot of conflicts with future patches >_<
Also, there's no external record of that code... I have to revert to a premake from 3 months ago to get at it.
If you want to move it out to a standalone module, we'd be happy to link to it. However, there's zero D expertise in the core group of maintainers.
I mean, I'm the 3rd or 4th largest committer to premake... it seems I was removed from the group due to inactivity, but you could still ask me for maintenance.
@premake/admins
My person perspective on this (not speaking for the team as a whole) - If something is in the core repo, there's an expectation of maintenance of it from a user perspective. The D module was a major blocker in removing the legacy gmake module, which has since been deprecated officially (and will be completely removed by 5.0 stable). I personally felt like removing gmake legacy was a much higher priority than maintaining D support, especially given the lack of knowledge. If the D logic could be ported out to a standalone module, I think there could be an argument made to bring it back to core, but I believe we made the right decision with the information we had at the time.
@TurkeyMan in #1099 you state "Do it" which I have always assumed was in response to "I looked into porting the D module and I'm now inclined to dropping it." Is this not what you meant? Also, on top of this, you should have been notified when @nickclark2016 posted there 2 years ago about removing the module. I appreciate where you're coming from, and I'm not opposed to the D module coming back but it becoming a permanent blocker for the rest of the project is not really acceptable.
Hmmm, yeah that was like almost 7 years ago, and my poor old ageing brain quite forgot about that! I actually did try to maintain this at the time, but the points in there about many:1 rules being a blocker were what stopped me from adapting this back then, was this ever resolved? If something happened there, then it would be possible to resolve and not make it a blocker anymore.
I'd actually quite like this, because gmake builds are important for me too; I have just carried on using the legacy gmake for all these years.
was this ever resolved?
It rings a bell, someone may have done something recently. It was only for MSBuild, but is this what you're looking for #2141?