OpenCore General Discussion

[ghost8282]

2 hours ago, Matgen84 said:

Hi @5T33Z0 I just watched: all Opencorepkg commits are build as usual on the Dortania repo. Only the one from February 24 is not in the repo. There were no commits between Feb 16 and Feb 23, so no build. 😊

 

2 hours ago, 5T33Z0 said:

That's not true. The last OC commit on the Dortanio Repo is ae04256 which is about 10 days old

 

That's true what Matgen84 said, I don't really know why you are saying it's not true...

 

There were no commits between 16 and 23 Feb.

Dortania lacks only the latest commit (who knows why?Ask them), which however adds nothing to the package.

 

46 minutes ago, 5T33Z0 said:

Because not everybody is a programmer

 

There's no need to be a programmer (I'm not...) when the only thing you have to do is to have xcode installed, download the source and run one single command ./build_oc.tool from the terminal.

 

Who doesn't want to compile himself can wait for releases, can wait for dortania, can wait for somebody else to publish compiled packages, otherwise if one wants to be independent and on the cutting edge, then...install the tools, use some processing power and compile yourself.

 

5 hours ago, 5T33Z0 said:

I've noticed that in the last 2 weeks a lot of errors are occurring under the "Actions" Tab of the OpenCorePkg Repo.

 

What fails is coverity in the latest automatic checks:
 

make: error: sh -c '/Applications/Xcode_12.4.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find make 2> /dev/null' failed with exit code 34304: (null) (errno=No such file or directory)
xcode-select: Failed to locate 'make', requesting installation of command line developer tools.

Being an ignorant, maybe something related to the setup on github, because it cannot find any command line developer tools.

All the latest builds compile perfectly fine.

Edited February 25, 2022 by ghost8282

[chris1111]

54 minutes ago, 5T33Z0 said:

@chris1111 Because not everybody is a programmer and has XTools installed and wants to waste processing power, time and energy to compile OpenCore,…I guess.

I think you undervalue yourself, you are very good at Hackintosh and you don't need to be a programmer for that

When you Installe Xcode and Command Line Tools from Apple Developper need Sign to developper

your not need to reinstall all stuf after macOS Update, you only to reopen Xcode then install componant

Its one Shot deal 

Edited February 25, 2022 by chris1111

[chris1111]

48 minutes ago, ghost8282 said:

 

make: error: sh -c '/Applications/Xcode_12.4.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find make 2> /dev/null' failed with exit code 34304: (null) (errno=No such file or directory)
xcode-select: Failed to locate 'make', requesting installation of command line developer tools.

Being an ignorant, maybe something related to the setup on github, because it cannot find any command line developer tools.

All the latest builds compile perfectly fine.

 

From Developer Command Line 12.4

https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_12.4/Command_Line_Tools_for_Xcode_12.4.dmg

 

[MaLd0n]

1 hour ago, ghost8282 said:

That's true what Matgen84 said, I don't really know why you are saying it's not true...

why not actions? Login Github and done

https://github.com/acidanthera/OpenCorePkg/actions

 

macOS XCODE5 Artifacts.zip

[ghost8282]

22 minutes ago, chris1111 said:

From Developer Command Line 12.4

https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_12.4/Command_Line_Tools_for_Xcode_12.4.dmg

Yes, I know, I was referring to the workflow error on github about coverity.

 

Thank you @MaLd0n I didn't know you could download compiled packages directly from there for every commit, however as I always did I prefer to compile all myself, but nice to know.

Edited February 25, 2022 by ghost8282

[chris1111]

For my part in the latest Beta I am using Xcode 13.2.1 and Command Line 13.2.1 for compille OpenCore

Edited February 25, 2022 by chris1111

[Guest 5T33Z0]

1 hour ago, ghost8282 said:

 

 

That's true what Matgen84 said, I don't really know why you are saying it's not true...

 

There were no commits between 16 and 23 Feb.

Dortania lacks only the latest commit (who knows why?Ask them), which however adds nothing to the package.

 

 

There's no need to be a programmer (I'm not...) when the only thing you have to do is to have xcode installed, download the source and run one single command ./build_oc.tool from the terminal.

 

Who doesn't want to compile himself can wait for releases, can wait for dortania, can wait for somebody else to publish compiled packages, otherwise if one wants to be independent and on the cutting edge, then...install the tools, use some processing power and compile yourself.

 

 

What fails is coverity in the latest automatic checks:
 

make: error: sh -c '/Applications/Xcode_12.4.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find make 2> /dev/null' failed with exit code 34304: (null) (errno=No such file or directory)
xcode-select: Failed to locate 'make', requesting installation of command line developer tools.

Being an ignorant, maybe something related to the setup on github, because it cannot find any command line developer tools.

All the latest builds compile perfectly fine.

 

You are aware that you are referencing a completely different repo, do you?
I am referencing this one: https://github.com/dortania/build-repo

And I said that twice now!

[ghost8282]

7 minutes ago, 5T33Z0 said:

I am referencing this one: https://github.com/dortania/build-repo

I know what I'm saying, I suggest to read again what Matgen84 wrote and what I wrote, I referenced the opencore repo nad dortania repo, saying that the dortania repo only lacks the latest commit.

What you are saying in your last message is a non sense to me.

Discussion closed for me

 

Edited February 25, 2022 by ghost8282

[Guest 5T33Z0]

I know how Xcode works. I know how Commandline Tools work. I am just not interested in Building OpenCore myself every day if it is available online!

 

My point was, that for the last 2 weeks I see a lot of error on the OpenCorepPkG repo and the builds on the dortania repo haven't been updated since 10 days.

 

And what I get in return: people trying to school me on Xcode and Command Line Tools – It's like me going to a barber shop asking for a haircut while in return the hairdresser is trying to sell me a perm…

[Matgen84]

41 minutes ago, 5T33Z0 said:

 

You are aware that you are referencing a completely different repo, do you?
I am referencing this one: https://github.com/dortania/build-repo

And I said that twice now!

 

Here is the correct Dortania repo, that's the one I was talking about. 😊
https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

[Guest 5T33Z0]

10 minutes ago, eSaF said:

Oh Man!!! - I wish I'd seen this before I went and built my own, anyway all is well as I put it through the usual tests and the build is good.

 

3 hours ago, Matgen84 said:

 

Here is the correct Dortania repo, that's the one I was talking about. 😊
https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

 

That's the same I was refering to all the time,  just filtered by releases and in a list view.

 

@eSaF I've been using this for more than a year now.

Edited February 25, 2022 by 5T33Z0

[ghost8282]

@eSaF take attention to Mald0n post:

filter by branch=master and event=push (unless you want to test other things like prs), and download directly compiled packages from acidanthera repo, instead of relying on third parties repos.

By this way if the package builds on compilers each commit will be compiled directly into acidanthera's repo and you can directly download the compiled package.

 

Instructions:

Spoiler

 

0) go to OpencorePkg Acidanthera's repo

1) Click on Actions

2) Click on Event and filter by "push"

 

 

 

3) Click on Branch and filter by "master"

4) Click on the description of a commit

 

 

5) Scroll down to the bottom and download a package of your choice: all should be functional what changes is the compiler with which opencore is compiled.

 

 

Edited February 25, 2022 by ghost8282

[Stefanalmare]

You guys are too smart for me. I just download the latest zip from https://github.com/acidanthera/OpenCorePkg. Double click build_duet.tool (I have BIOS hacks), double click build_oc.tool, and in Binaries I have in the latest OC (Debug and Release). Some scripts to build latest kexts and this is what I do before each update/upgrade.

Edited February 25, 2022 by Stefanalmare

[Avery B]

Main pro of the dortania builds is that you don't need to login. Less out of the way as github action builds as well (though this is minor).
Other main pro is that you can go build by build if you need to test where something broke, and they don't expire after ~30 days or whatever the timeout is on github.

[deeveedee]

On 2/25/2022 at 3:24 AM, 5T33Z0 said:

... the last bOC uild available on the Dortania Repo is also about 10 days old. I wonder what's going on. 

 

Staying safe and busy protesting, I hope.

 

Thoughts and prayers to all those affected by the atrocities in Ukraine.

Edited February 26, 2022 by deeveedee

[miliuco]

On 2/25/2022 at 10:06 PM, Stefanalmare said:

https://github.com/acidanthera/OpenCorePkg.

Last dot of the link is included into it and gives error, only to be noticed.

[MorenoAv]

Hi guys,

I have a problem, my Windows 11 ssd, don't appear in OpenCore picker at start although I have ScanPolicy =0, how do I solve this?

Thanks

[Anto65]

Am I wrong or the Win EFI partition is missing?

[MorenoAv]

Thanks Guys, I'll re-install it, one more time... 

[Anto65]

Sorry but did you install after Windows?

[Anto65]

Windows being lazy 😁 , if it finds the EFI ready it does not create its own but goes to rely on an existing one (  for this I disable the other disks from the bios even with linux )  have you seen if it has somewhere saved the Microsot folder? in case you should copy it in the EFI from which you start together with OC .... Usually it resolves like this

[MorenoAv]

First I installed Windows 11, with my ssd nvme for macOS Monterey empty, after that I removed my ssd sata with Windows 11 and installed macOS Monterey after that plugged the ssd sata with macOS Big Sur and after that I don't know how I lost my Windows EFI...

After re reading your post I recall that I deleted the EFI from the Windows from my ssd with macOS Monterey...

For that reason re install it is... 

[Avery B]

Even if the SSD looked empty, it might have had an EFI partition. Windows will shove the EFI on the first EFI partition it finds, so try to disconnect/disable all other drives in your BIOS when installing W11. Failing that, there are ways to manually install windows through command line in recovery. If it ends up on another disk, I don't think it's the end of the world as OpenCore should be able to detect it anyways. Just be careful of EFI/BOOT being replaced with Windows's BOOTx64.efi on that disk.

[Guest 5T33Z0]

Since the last nightly build I can only move the cursor in the between 2 entries with the Keyboard, in the Bootpicker. I have 4 entries, though. And wherever I move the cursor this limits the cursor between these 2 entries. Really weird.

[hardcorehenry]

36 minutes ago, 5T33Z0 said:

Since the last nightly build I can only move the cursor in the between 2 entries with the Keyboard, in the Bootpicker. I have 4 entries, though. And wherever I move the cursor this limits the cursor between these 2 entries. Really weird.

 

Have the same issue, try with arrows. After each “left” or “right” I had to press space. Weird, but for sure it’ll be corrected.

 

EDIT: Also set the default boot option(CTRL+Enter and CTRL+Index) stopped working.

 

Edited March 2, 2022 by hardcorehenry