If I recall, there are multiple stages to the build (at least 2) to get actual EFI binaries, right?
I messed around just a little bit, but couldn’t decide if I wanted to
- figure out how to package the UDK itself: not so simple/neat since it looks like you build everything within the tree, but with the chance that the UDK itself would be useful in itself as a development tool made that worth considering.
- download the UDK, build the binaries and discard everything but the final product of interest (with the possibility of making any number of subpackages to include other useful products of the build)
By the time UDK 2017 was released (originally slated for early Q1 2017… HA!) I no longer had the time I’d posessed when I started using Void, so I didn’t bother seeking out opinions/advice. (though I presently think #2 is the best option; the UDK really seems like one of those projects that if you’re going to actually use to develop other software, you’d do it standalone in your home directory or a git fork, like you would a project inside an IDE).
Quite interesting to me that here we are quite some time later, and you’re actually the first person I’ve seen here who has expressed an interest in having OVMF binaries built in Void. (well OVMF has been mentioned on occasion, but I’m pretty sure you’re the first person I’ve seen to mention downloading and actually testing the build process).
I like your willingness to try. It’s refreshing.
And I suspect that at least a few people would be happy to see OVMF binaries provided in Void,