Clover General discussion

[MakAsrock]

I checked everything four times and found no errors or warnings. I was unable to obtain Xcode 16 legally. Thank you and good luck! 
Official instructions:
Build Clover on macOS Tahoe 26 from scratch.

    •    Install Xcode 26 or Xcode 16, Make sure you open Xcode then Install additional required components.
    •    Install Python 3.11.5 or Python 3.13.7
[🍀] ⬇︎ Clone and Build Clover

rm -rf ~/src
mkdir -p ~/src
cd ~/src
git clone https://github.com/CloverHackyColor/CloverBootloader.git
cd ~/src/CloverBootloader && ./buildme

buildme Option:⬇︎

    1    build Clover (Default Toolchain)
    2    make pkg
No other methods are discussed or supported by the authors and no claims will be accepted.

Edited October 4, 2025 by MakAsrock

[Max.1974]

41 minutes ago, MakAsrock said:

I checked everything four times and found no errors or warnings. I was unable to obtain Xcode 16 legally. Thank you and good luck! 
Official instructions:
Build Clover on macOS Tahoe 26 from scratch.

    •    Install Xcode 26 or Xcode 16, Make sure you open Xcode then Install additional required components.
    •    Install Python 3.11.5 or Python 3.13.7
[🍀] ⬇︎ Clone and Build Clover

rm -rf ~/src
mkdir -p ~/src
cd ~/src
git clone https://github.com/CloverHackyColor/CloverBootloader.git
cd ~/src/CloverBootloader && ./buildme

buildme Option:⬇︎

    1    build Clover (Default Toolchain)
    2    make pkg
No other methods are discussed or supported by the authors and no claims will be accepted.

 

If you trust me, this file is the zip downloaded directly from Apple’s developer website. If you can’t access it:

 

https://www.mediafire.com/file/it564ypd8q5wava/Xcode_16.4-melhor.xip/file 

 

 

[MakAsrock]

1 hour ago, Max.1974 said:

 

If you trust me, this file is the zip downloaded directly from Apple’s developer website. If you can’t access it:

 

https://www.mediafire.com/file/it564ypd8q5wava/Xcode_16.4-melhor.xip/file 

 

 

Thank you very much. I'm already downloading it, but how can I prevent it from updating? So far I can say that it builds with Python 3.13.7 + Xcode_26.0.1  and  Python 3.9 + Xcode_15.3 🙂

Edited October 4, 2025 by MakAsrock

[chris1111]

4 hours ago, Max.1974 said:

Hi @chris1111 

 

Hello my dear friend, the Clover Builder was designed to update Python and also reuse binaries, avoiding the time-consuming process of downloading and reconfiguring GCC. But thank God the Git from Clover was updated — that makes things much easier for everyone. I’d like to emphasize that the tool doesn’t change the essence of Clover; it simply gives us options to update, refresh, or re-clone the Clover folder from scratch, and helps prevent common errors that occur with each Xcode or macOS change. Thank you for keeping Clover up to date. Everything compiled perfectly here.

 

 

 

 

 

Thanks my good freind 😀

Really appreciate that you taking time

You can use any script you want thats not a probleme, I just clarified simply how to for the newbie.

[MakAsrock]

46 minutes ago, chris1111 said:

Thanks my good freind 😀

Really appreciate that you taking time

You can use any script you want thats not a probleme, I just clarified simply how to for the newbie.

Everything came together perfectly but buildme was never fixed and I remain on my semi-synchronized branch. Thanks everyone.

Edited October 4, 2025 by MakAsrock

[Max.1974]

1 hour ago, MakAsrock said:

Thank you very much. I'm already downloading it, but how can I prevent it from updating? So far I can say that it builds with Python 3.13.7 + Xcode_26.0.1  and  Python 3.9 + Xcode_15.3 🙂

 

For me works disable this two toggles  :

 

[MakAsrock]

1 hour ago, Max.1974 said:

 

For me works disable this two toggles  :

 

I came up with another way. I just renamed it to Xcode16.4 and before compilation I rename the required one in Xcode.

[Max.1974]

1 hour ago, MakAsrock said:

I came up with another way. I just renamed it to Xcode16.4 and before compilation I rename the required one in Xcode.

Yes my friend, is another way to do it !! Nice shot!!   

You can have many Xcode installed, just renamed correctly 

[chris1111]

11 hours ago, Max.1974 said:

Yes my friend, is another way to do it !! Nice shot!!   

You can have many Xcode installed, just renamed correctly 

 

You dont need to rename anything

Put Xcode 16 in a folder like this

Spoiler

 

 

Open Applications Xcode 26 ➥ Settings ➥ Locations ➥ Command Line Tools  ➥ Choose the Xcode 16.4 (16F6)

 

 

 

You can change to Xcode 26 anytime

 

 

Edited October 5, 2025 by chris1111

[Max.1974]

Thanks my brother @chris1111 very  nice !  

[MakAsrock]

8 hours ago, chris1111 said:

 

You dont need to rename anything

Put Xcode 16 in a folder like this

Open Applications Xcode 26 ➥ Settings ➥ Locations ➥ Command Line Tools  ➥ Choose the Xcode 16.4 (16F6)

You can change to Xcode 26 anytime

 

 

Thanks friend, that's what I did. 👍🤝

[Matgen84]

On 10/4/2025 at 3:42 PM, chris1111 said:

To All Build Clover on macOS Tahoe 26 from scratch 

This instructions will build Clover without external build script

✌️

 

Thanks @chris1111 @MakAsrock 

Since few years and in Build_Clover_Sequoia.txt in Clover Git repo, because of submodule Opencorepkg,  git clone command is:

git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git

Is it always available on macOS 26 Tahoe ?

Build_Clover_in_Sequoia.txt

[MakAsrock]

15 minutes ago, Matgen84 said:

 

Thanks @chris1111 @MakAsrock 

Since few years and in Build_Clover_Sequoia.txt in Clover Git repo, because of submodule Opencorepkg,  git clone command is:

git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git

Is it always available on macOS 26 Tahoe ?

Build_Clover_in_Sequoia.txt 404 B · 0 downloads

I couldn't get it to work for Tahoe exactly as described here. So I wrote a separate Build_Clover_Sequoia.md and added chris1111's Build_Clover_Tahoe.md , but I rewrote the links to my repository, which is already several commits ahead of the parent.
Now my branch is more advanced than the main one, both in terms of stability and functionality. All my pull requests on the master branch are ignored. And I will not synchronize with it.

Edited October 5, 2025 by MakAsrock

[chris1111]

No more need CloverBuildTools from external repos

All the GNU tools is downloading fast 

https://github.com/CloverHackyColor/CloverBootloader/commit/0f33d59b6f076bee2c95258f41e389e62ea8bc1f

 

I suggest to the Users to restart building from scratch 

Enjoy! ✌️

[chris1111]

4 hours ago, Matgen84 said:

 

Thanks @chris1111 

Since few years and in Build_Clover_Sequoia.txt in Clover Git repo, because of submodule Opencorepkg,  git clone command is:

git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git

Is it always available on macOS 26 Tahoe ?

Build_Clover_in_Sequoia.txt 404 B · 1 download

Build_Clover_Tahoe.md probably work from BigSur to Tahoe because git clone OpenCore is included in buildme

Edited October 5, 2025 by chris1111

[Max.1974]

Hello everyone, I’ve uploaded the Clover Compiler Builder v14 to GitHub for anyone interested, and there’s also the full git clone available to install the app on your computer as well. And release too. 

 

Since the Clover buildme is now fixed, it’s easier for me to handle any changes in the project as needed, and I use Cursor directly for the commits of the Clover Compiler Builder, if necessary.

 

https://github.com/maxpicelli/Clover-Compiler-Builder 

 

or in Terminal: 

curl -fsSL https://raw.githubusercontent.com/maxpicelli/Clover-Compiler-Builder/main/setup.sh | bash

 

App still with English instructions  

 

 

Edited October 5, 2025 by Max.1974

[MakAsrock]

1 hour ago, Max.1974 said:

 

Hello everyone, I’ve uploaded the Clover Compiler Builder v14 to GitHub for anyone interested, and there’s also the full git clone available to install the app on your computer as well. And release too. 

 

https://github.com/maxpicelli/Clover-Compiler-Builder 

 

 

For some time now, no third-party tools are required to build Clover. Simply navigate to the src folder and run the command:
git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git
or even better:
git clone --recurse-submodule https://github.com/YBronst/CloverBootloader.git
From this link, you'll download a more stable version, including all the latest changes and patches.
Furthermore, such tools can interfere and hinder compilation.

As an alternative, I suggest my Clover cloner.

Da qualche tempo, non sono più necessari strumenti di terze parti per compilare Clover. Basta andare nella cartella src ed eseguire il comando:
git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git
o, ancora meglio:
git clone --recurse-submodule https://github.com/YBronst/CloverBootloader.git
Da questo link, scaricherete una versione più stabile, che include tutte le ultime modifiche e patch.
Inoltre, tali strumenti possono interferire e ostacolare la compilazione.

In alternativa, consiglio il mio Clover Cloner.

Grazie signore!

Clover cloner.zip

Edited October 5, 2025 by MakAsrock

[Max.1974]

1 hour ago, MakAsrock said:

Há algum tempo, nenhuma ferramenta de terceiros é necessária para construir o Clover. Basta navegar até a pasta src e executar o comando:
git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git
ou melhor ainda:
git clone --recurse-submodule https://github.com/YBronst/CloverBootloader.git
A partir deste link, você baixará uma versão mais estável, incluindo todas as alterações e patches mais recentes.
Além disso, tais ferramentas podem interferir e dificultar a compilação.

Como alternativa, sugiro meu cloner Clover.

Há alguns tempos, não são mais necessárias ferramentas de terceiros para compilar Clover. Basta entrar na pasta src e executar o comando:
git clone --recurse-submodule https://github.com/CloverHackyColor/CloverBootloader.git
O, ainda melhor:
git clone --recurse-submodule https://github.com/YBronst/CloverBootloader.git
A partir deste link, você baixará uma versão mais estável, que inclui todas as últimas modificações e patches.
Além disso, tais ferramentas podem interferir e dificultar a compilação.

Como alternativa, recomendo o meu Clover Cloner.

Obrigado, senhor!

 

@MakAsrock  thank you, my friend.

 

My tool is certainly not meant to be an innovation, but rather a support utility for installing and cloning Clover. That’s why I made it optional for users to choose — whether to delete and clone a new repo, reuse the existing one, update only the original Clover git, or simply save the binaries. Nothing more than that.

 

I hope you understand that Clover buildme doesn’t offer these options, nor does it check for Python or allow using Anaconda Python 3.9.6 as the main interpreter instead of the standard Python 13.5.+. So, it’s no longer necessary — but my workflow runs in parallel. It’s not a new compiler, and that was never the intention. I hope this clarifies things, since it seems there’s been some confusion about it since its creation.  

 

Your tool delete folder without ask what to do with all files, included binaries: 

 

And as you can see, your tool automatically deletes the originally downloaded Clover — it removes the entire folder without even asking whether the user wants to save it or not. This ends up wasting a lot of time when we need to rebuild everything from scratch.

 

That’s exactly what I’m trying to address with Clover Builder: it provides options and flexibility that none of the existing scripts — not even the original git clone process — currently offer.

Edited October 5, 2025 by Max.1974

[Max.1974]

 

1. This is what my app asks

 

 

 

 

 

 

 

So, the name Clover Builder is only suggestive — it’s not meant to compile anything new or modify the original source code in any way. Its purpose is to work alongside the existing tools, helping in situations that I consider practical and useful. It will never change or interfere with the original Clover buildme source code.

I hope that, once clarified, the purpose of this tool won’t be misunderstood anymore. I truly appreciate your work.

Edited October 5, 2025 by Max.1974

[Max.1974]

 

2. Create perfectly using the original scripts from the original git clone

 

 

 

 

 

 

 

 

Edited October 5, 2025 by Max.1974

[chris1111]

✌️

Edited October 6, 2025 by chris1111

[MakAsrock]

8 hours ago, Max.1974 said:

 

@MakAsrock  thank you, my friend.

 

My tool is certainly not meant to be an innovation, but rather a support utility for installing and cloning Clover. That’s why I made it optional for users to choose — whether to delete and clone a new repo, reuse the existing one, update only the original Clover git, or simply save the binaries. Nothing more than that.

 

I hope you understand that Clover buildme doesn’t offer these options, nor does it check for Python or allow using Anaconda Python 3.9.6 as the main interpreter instead of the standard Python 13.5.+. So, it’s no longer necessary — but my workflow runs in parallel. It’s not a new compiler, and that was never the intention. I hope this clarifies things, since it seems there’s been some confusion about it since its creation.  

 

Your tool delete folder without ask what to do with all files, included binaries: 

 

And as you can see, your tool automatically deletes the originally downloaded Clover — it removes the entire folder without even asking whether the user wants to save it or not. This ends up wasting a lot of time when we need to rebuild everything from scratch.

 

That’s exactly what I’m trying to address with Clover Builder: it provides options and flexibility that none of the existing scripts — not even the original git clone process — currently offer.

My utility does indeed delete the entire Clover folder, but if you answered yes, it preserves the tools/download folder, even though this is no longer necessary since the new build_gcc15.sh downloads everything it needs from fast servers. However, as you correctly noted, it doesn't check whether Python is installed. Your tool installs HomeBrew and the Python package it comes with. On macOS versions prior to Sequoia, this was acceptable, but on Sequoia and especially Tahoe, it resulted in the error many people have recently complained about. That's why I left the decision to install Python up to the user. Thank you friend!

[MakAsrock]

2 hours ago, MakAsrock said:

My utility does indeed delete the entire Clover folder, but if you answered yes, it preserves the tools/download folder, even though this is no longer necessary since the new build_gcc15.sh downloads everything it needs from fast servers. However, as you correctly noted, it doesn't check whether Python is installed. Your tool installs HomeBrew and the Python package it comes with. On macOS versions prior to Sequoia, this was acceptable, but on Sequoia and especially Tahoe, it resulted in the error many people have recently complained about. That's why I left the decision to install Python up to the user. Thank you friend!

The current version of your script is completely correct and ready to use.

What the utility does:

correctly checks Xcode and Python,

safely processes an existing directory:

Asks whether to delete the CloverBootloader folder and if the answer is no, exits.

clones the repository with submodules,

produces the final build instructions.

Clover cloner.zip

[Max.1974]

3 hours ago, MakAsrock said:

My utility does indeed delete the entire Clover folder, but if you answered yes, it preserves the tools/download folder, even though this is no longer necessary since the new build_gcc15.sh downloads everything it needs from fast servers. However, as you correctly noted, it doesn't check whether Python is installed. Your tool installs HomeBrew and the Python package it comes with. On macOS versions prior to Sequoia, this was acceptable, but on Sequoia and especially Tahoe, it resulted in the error many people have recently complained about. That's why I left the decision to install Python up to the user. Thank you friend!

Yes. Congrats too. I never receive reclaim about python because works fine with anyone code. I prefere use Anaconda. Not fail anymore. Fail was with Xcode 26. 

[MakAsrock]

57 minutes ago, Max.1974 said:

Yes. Congrats too. I never receive reclaim about python because works fine with anyone code. I prefere use Anaconda. Not fail anymore. Fail was with Xcode 26. 

We're not saying that you can't compile with Anaconda or Miniconda, or with other forks, but we're just saying how to avoid the error:
[BUILD CloverV2]
fatal: '1': not an integer
With Xcode >= 16, it doesn't work.
This doesn't apply to macOS 14, where everything compiles fine even with Anaconda or Miniconda.
However, for example, in macOS Ventura 13, installing any Python other than the built-in one also breaks the compilation.
At least for me. I'm not saying that others might have different experiences. But I can't recommend the paths that lead to errors for me.
Why? Ask Slice, but I can't, because he doesn't answer me. Yes, from a certain point on, I don’t even want to ask.
I've been blocked on the website https://www.applelife.ru for some time now for political reasons.

After the block expires, I plan to delete my account from there.

Edited October 6, 2025 by MakAsrock