Jump to content

OpenCore General Discussion


dgsga
8,887 posts in this topic

Recommended Posts

I can't seem to boot, just hangs can someone look at my EFI and maybe point me in right direction, Thanks

 

Edited by STLVNUB
Link to comment
Share on other sites

One thing I've noticed regarding Kexts

Why the need for an Executable path? Plist Path?

Majority of kexts have Executable as same name as kext.

The path is always the same too, so no need for that.

Common Path Contents/MacOS/

Common Plist Contents/Info.plist

e.g Use Common Path and the kext name as the Executable

Common Plist for the....Plist

 

Bundle Path FTS.kext

Enabled.     Yes

Comment    Why is it so

 

so basically reduce code to 2 or 3 lines.

 

  • Like 2
Link to comment
Share on other sites

7 minutes ago, n.d.k said:

Hi guys,

 

How do I include the AppleSupportPkg in OpenCorePkg, so it can compile all at once?

 

I did see the ocbuild.config added in the AppleSupportPkg, I assumed I can git clone the pkg into the UDK folder.

 

What's the correct way of doing it?

https://github.com/Pavo-IM/ocbuilder/releases

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

14 minutes ago, n.d.k said:

Can't seems to compile VirtualSMC atm, got like 4 fails due to missing header file

 

Take a look at @Pavo reply: ocbuiilder compile OC + all Lilu plugins at once time. VirtualSMC standalone: just download latest release 1.0.7. If you only want to build VirtualSMC: do you put latest Lilu Debug in VirtualSMC before compling?

Edited by Matgen84
  • Thanks 1
Link to comment
Share on other sites

Down to 1 fail after I copied Lilu header folder to VirtualSMC :(

 

Problem solved:

I need to copy the Lilu.kext into VirtualSMC folder. Build succeeded! :)  Thanks to Matgen84 and Pavo. 

Edited by n.d.k
Problem solved
  • Like 1
Link to comment
Share on other sites

I managed to solve a lot fails by looking at the comments and reading the manual.

 

i have one single fail left that i couldn't find anything about it:

 

OCB: Failed to match a default boot option.

 

EDIT: to be clear, the system does boot and all, is just that line appears before booting and is bothering me. 

Edited by ham4ever
Link to comment
Share on other sites

10 minutes ago, Download-Fritz said:

@STLVNUB Explicitly defining the executable and PLIST paths is done for security and not for technical reasons

Thats all very well, if the user WANTS the added security, most probably want simplicity, you guys making it way harder than it should be

Link to comment
Share on other sites

×
×
  • Create New...