the-braveknight
Moderator
- Joined
- Nov 24, 2015
- Messages
- 1,220
- Motherboard
- Lenovo Legion Y520 (Clover)
- CPU
- i7-7700HQ
- Graphics
- HD 630 (1920x1080) + Nvidia GTX 1060
- Mac
- Mobile Phone
I made my own build too and I've been testing it. But I prefer to wait for an official release so that I can avoid uploading pre-built binaries to the repo when it is supposed to contain pure code.I made two PRs for two different codecs discovered (so far) with the Probook guide.
I gave up waiting for a build and just included my fixed build in the repo.
When a new build appears with the fixes, I'll remove my build and download theirs.
BTW, you might want to take a look at some of the recent additions to my hack-tools github project.
I added a LiluFriend generator (and a second technique of my own, LiluFriendLite).
Although I'm not 100% convinced LiluFriend is required, vit9696 recommends it when you install Lilu kexts to /L/E or /S/L/E.
The script automatically scans for Lilu-based kexts that are installed and sets up the OSBundleLibraries dependencies that match.
LiluFriend.kext has always confused me. I've never encountered any problems with Lilu and its plugin kexts installed to /L/E so I've never really felt I needed LiluFriend.kext.
However, I can see that your LiluFriendLite.kext is a codeless kext (Info.plist only), and my understanding is that it has to be regenerated every time we want to install a new Lilu plugin, right?
Also, do you still think it's a bad idea to have the required kexts injected by Clover instead of installing them to system locations?