Usage
OC-tool will use a config.plist file placed in the INPUT folder to make the OUTPUT EFI folder. If a path to an existing EFI folder, or a path to a folder containing a config.plist is given as a command line argument, OC-tool will use that config.plist instead.
Double clicking OC-tool in the Finder is the same as running ./OC-tool -o from the command line
-d
prebuilt daily - makes an EFI using prebuilt daily repos
-h
help - shows the help text and then exits
-i
ignore - ignores a resource if it does not exist in the .tool-files/git_repo.json or extras directory
useful for checking on missing files or config.plist issues
-n
no scan - do not scan config.plist for missing/extra fields
-o
open - opens up to the new EFI folder in macOS Finder when the build is complete
-q
quiet - suppress output messages on the command line
-s
latest source - build from source instead of using prebuilts
-t
Text based User Interface - visually enable/disable kexts, drivers and quirks, get descriptions of files and quirks, and see potential issues
-v
verbose - lowercase v - output all messages to the screen instead of the log file
-C
Custom - uppercase C - use SampleCustom.plist when scanning for missing/extra fields in the INPUT config.plist
-D
Debug - uppercase D - build DEBUG version of OpenCore, drivers and kexts instead of RELEASE version
-N
no updates - uppercase N - do not look for updates or download any files before building, just build from current local resources if possible
-V
Version - uppercase V - print the version info then exit
-X
remove - uppercase X - removes the downloaded/built resources stored in the resources directory