rusty-bits / octool Goto Github PK

If I set True or False I'm still getting an error. still boots without issues.

Thanks

1] Getting a config.plist error but boots without issues
2] can't find the listed errors in the config.plist
3] octool not generating a log file

Thanks

After a long hiatus on the OSX scene, I am back, and decided to give your rust-based tool a shot. Being able to run it purely on console is what keeps me hooked in. I'm impressed on how easy it is to do what it does, however coming from your old shell based tool, a bit sad on how limited it currently feels. It seems this tool aggregate files from Dortania, with a nice front-end to the ocvalidate tool. The option to specify on the fly which version of OC to use is great, but not sure if allowing usage of a previous version has any implications with newer Lilu and friends - should not, but again, keyword should.

One great advantage your previous shell code had was the ability to compile modules from their sources. Any chances of this feature to make a come back?

Another "missing" feature is the ability to add other extension sources (such as VoodooI2C) into a list of extensions to be fetched online. Not sure how easy (or feasible) would be to add them to the config.json manually - perhaps via a "custom.json" file added into the INPUT/ folder and read during build time to make it less prone to be overwritten during updates.

On the octool update front, it seems (from a comment on another issue) your tool does not auto update, since it is a binary file. Perhaps you could add the compiled binaries into the git repository, with their respective checksums, and add a call to fetch and process these files during a self updating routine. Makes for a more user-friendly experience.

Keep up with the great work, and thank you for the tool!

it seems to try to treat my -o 0.7.6 input as the config.plist argument

`
% ./octool -o 0.7.6

Did not find config at "/Users/bkmartin/opencore/octool/-o"
Using tool_config_files/OpenCorePkg/Docs/Sample.plist
`

I don't know if this topic has already been discovered or not but... In case you wanna use a custom Resources folder (e.g. no Audio folder or dropped themes) it would be very convenient to specify a custom Resources folder in INPUT directory that will be copied during the EFI building process.
What do you think about it? Is this thing achievable?
Greetings
dreamwhite

I decided to give octool another try. Updated opencore to 0.7.6, worked perfectly.

The only kext I added to the input was the recently released RadeonSensor.kext. would it be possible for octool to pull it from the repo?

Thank You

The new driver efi files for ResetNvramEntry.efi and ToggleSipEntry.efi have to be in the input directory. They are not fetched automatically. Also the obsolete entries are not removed.

Thank you so much for the effort you're putting in this project.
It would be very useful having a add template for the following entries in the config.plist:

• ACPI/Delete
• ACPI/Patch
• Booter/MmioWhitelist
• Booter/Patch
• DeviceProperties/Add
• Kernel/Block
• Kernel/Force
• Kernel/Patch
• Misc/BlessOverride
• Misc/Entries

What are your thoughts on this? Is this thing achievable?
Greetings
dreamwhite

Hi rusty 😄 ,

Maybe theres an update needed for 0.9.0 ?
Or is there reaaly something wrong with the hash?
They are equal.

Checking local OpenCorePkg 0.9.0 binaries ... "OpenCore-0.9.0-RELEASE" local copy not found, Downloading
remote hash 156fc6371e07dc17c3363e5da1812c1df5355782e1f5e1895b3ded3be1b8158b
  local sum a036578d90d783bde5aad5be6f4eb8b9b1569e67e748f1f381cb2713b3f633fa
thread 'main' panicked at 'Sum of "resources/OpenCore-0.9.0-RELEASE/OpenCore-0.9.0-RELEASE.zip" does not match 156fc6371e07dc17c3363e5da1812c1df5355782e1f5e1895b3ded3be1b8158b', src/res.rs:285:13
                             note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
                                                                                                          zsh: abort      ./octool -V 0.9.0

regards,
Henk

Hello
I was wondering if this tool is able to update the config.plist like your previous tool?
Thanks.

Hi,
I'm finding this version confusing not sure where I'm going wrong

Thanks