Clover General discussion

[Matgen84]

Hi @chris1111 @Slice

When I launch buildme from CloverBootloader, two banners appears. I don't under stand why. See below. Please.
Note: only Python 3.13.0 is installed.

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 64d434947)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 -------------------- 
Updating OpenCorePkg....

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 4e0ec07ff)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.0 -------------------- 

 

[chris1111]

1 hour ago, Matgen84 said:

Hi @chris1111 @Slice

When I launch buildme from CloverBootloader, two banners appears. I don't under stand why. See below. Please.
Note: only Python 3.13.0 is installed.

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 64d434947)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 -------------------- 
Updating OpenCorePkg....

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 4e0ec07ff)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.0 -------------------- 

 

 

@Matgen84 I haven't touched BuildMe, I've never touched it.
Ask @MakAsrock, personally, I don't have your problem.

 

[Matgen84]

27 minutes ago, chris1111 said:

 

@Matgen84 I haven't touched BuildMe, I've never touched it.
Ask @MakAsrock, personally, I don't have your problem.

 

 

@chris1111 maybe, it's a graphic issue: Nvidia Kepler root patched on my Ivybridge machine under Sequoia. 

[Max.1974]

4 hours ago, Matgen84 said:

Hi @chris1111 @Slice

When I launch buildme from CloverBootloader, two banners appears. I don't under stand why. See below. Please.
Note: only Python 3.13.0 is installed.

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 64d434947)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 -------------------- 
Updating OpenCorePkg....

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 4e0ec07ff)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.0 -------------------- 

 

 

Hi @Matgen84 

 

Why it happens: Multiple Python installations cause conflicts because different versions may have incompatible libraries, PATH confusion, and packages installed in different locations.

Solution - Remove one instance:

 

# Find Python locations
which python3
ls -la /usr/bin/python*
ls -la /usr/local/bin/python*

# Check versions
python3 --version
/usr/bin/python3 --version
/usr/local/bin/python3 --version

Remove homebrew Python (if installed via brew):

brew uninstall python@3.13

Or remove manually installed Python:

# Remove from Applications (macOS)
sudo rm -rf /Applications/Python\ 3.13/

# Remove from usr/local
sudo rm -rf /usr/local/bin/python3.13*
sudo rm -rf /usr/local/lib/python3.13*

Clean PATH configuration:

# Edit shell profile (.zshrc or .bash_profile)

nano ~/.zshrc

# Remove any Python-related PATH exports

Complete removal:

# Remove all Python versions
brew uninstall --ignore-dependencies python@3.13
brew uninstall --ignore-dependencies python@3.12
sudo rm -rf /Applications/Python*
sudo rm -rf /usr/local/bin/python*
sudo rm -rf /usr/local/lib/python*

Fresh installation:

# Install via Homebrew (recommended)
brew install python@3.13

# Or download from python.org

 

Check 

 

which python3
python3 --version
pip3 --version

 

I use Anaconda Python to compile for older macOS versions, such as Ventura. This is important information because Anaconda Python is specifically chosen for backward compatibility with older macOS versions like Ventura. This means simply removing/reinstalling might not be the best solution since Anaconda serves a specific purpose for cross-version compilation support.

 

 

[Max.1974]

If the problem is  xbuildme script, you can shows hardcoded Python version causing confusion during builds

 

Option 1 - Check current line:

sed -n '87p' xbuildme

 

Option 2 - Auto-detect Python version:

Backup first cp xbuildme xbuildme.backup # Make script detect version automatically

 

sed -i '' 's/Python 3.13.7/Python $(python3 --version 2>\&1 | cut -d" " -f2)/g' xbuildme

 

Option 3 - Remove version display (recommended):

Comment out line 87 to hide Python version

 

sed -i '' '87s/^/#/' xbuildme

 

Option 4 - Verify changes:

 

sed -n '87p' xbuildme

 

Result: Eliminates confusing output showing multiple Python versions during Clover bootloader builds. Choose Option 3 to completely hide version info or Option 2 to show actual system version.

[Matgen84]

@Max.1974

I make a Python 3.13.7 clean install (download version from python.org):

 

mathieu@Mac-Pro-de-mathieu ~ % which python3
/Library/Frameworks/Python.framework/Versions/3.13/bin/python3
mathieu@Mac-Pro-de-mathieu ~ % python3 --version
Python 3.13.7
mathieu@Mac-Pro-de-mathieu ~ % pip3 --version
pip 25.2 from /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pip (python 3.13)

Despite of that : Display menu appears twice, with two different commits.

 

Spoiler

---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 64d434947)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 -------------------- 
Updating OpenCorePkg....

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 4e0ec07ff)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 ------------------

 

 

I don't use xbuildme script. But with it, only one Display menu:

 

Spoiler

---------------------------------------------------------------------------------

                           🍀 Clover r5163 (SHA: 64d434947)

                              Default TOOLCHAIN: GCC151

                     Switch to XCODE select: build (with XCode)

     Depending on your XCODE version the Toolset will be automatically chosen

---------------------- Current Python version: Python 3.13.7 --------------------

 

------------------------------------------------------------------------

cat: vers.txt: No such file or directory

buildme, Clover v5 r (SHA: 4e0ec07ff)

TOOLCHAIN: GCC151 (override example: './buildme GCC53')

 

1) build Clover

2) make pkg

3) make iso

4) build all

5) test build (no autogen, no boot files)

6) status

7) update Clover

😎 update Clover (reset changes)

9) show diff

10) open drivers directory

11) clean BaseTools

12) quit

Please enter your choice:

 

 

Edited September 10, 2025 by Matgen84

[Slice]

The script buildme is broken. Use xbuildme. One nonsense is green text 🙃

[MakAsrock]

8 hours ago, chris1111 said:

 

@Matgen84 I haven't touched BuildMe, I've never touched it.
Ask @MakAsrock, personally, I don't have your problem.

 

This has been the case for as long as I can remember. Once it shows a banner with what was there, and the second time with what is after the update. As for the interface, I did not touch it.

[Max.1974]

13 hours ago, Matgen84 said:

@Max.1974

I make a Python 3.13.7 clean install (download version from python.org):

 

mathieu@Mac-Pro-de-mathieu ~ % which python3
/Library/Frameworks/Python.framework/Versions/3.13/bin/python3
mathieu@Mac-Pro-de-mathieu ~ % python3 --version
Python 3.13.7
mathieu@Mac-Pro-de-mathieu ~ % pip3 --version
pip 25.2 from /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pip (python 3.13)

Despite of that : Display menu appears twice, with two different commits.

 

  Hide contents

---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 64d434947)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 -------------------- 
Updating OpenCorePkg....

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 4e0ec07ff)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 ------------------

 

 

I don't use xbuildme script. But with it, only one Display menu:

 

  Hide contents

---------------------------------------------------------------------------------

                           🍀 Clover r5163 (SHA: 64d434947)

                              Default TOOLCHAIN: GCC151

                     Switch to XCODE select: build (with XCode)

     Depending on your XCODE version the Toolset will be automatically chosen

---------------------- Current Python version: Python 3.13.7 --------------------

 

------------------------------------------------------------------------

cat: vers.txt: No such file or directory

buildme, Clover v5 r (SHA: 4e0ec07ff)

TOOLCHAIN: GCC151 (override example: './buildme GCC53')

 

1) build Clover

2) make pkg

3) make iso

4) build all

5) test build (no autogen, no boot files)

6) status

7) update Clover

😎 update Clover (reset changes)

9) show diff

10) open drivers directory

11) clean BaseTools

12) quit

Please enter your choice:

 

 

 

@Matgen84 

 

You can compile with xbuildme, as Slice said. I compiled it in three different ways and none had any problems. Basically, you can use it with both scripts, but it will only recognize one in the end.

It doesn't generate any fatality (apparently) nor will it interfere with the compilation.  

[MakAsrock]

On 9/10/2025 at 12:06 PM, Matgen84 said:

Hi @chris1111 @Slice

When I launch buildme from CloverBootloader, two banners appears. I don't under stand why. See below. Please.
Note: only Python 3.13.0 is installed.

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 64d434947)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.7 -------------------- 
Updating OpenCorePkg....

 ---------------------------------------------------------------------------------
                           🍀 Clover r5163 (SHA: 4e0ec07ff)
                              Default TOOLCHAIN: GCC151
                     Switch to XCODE select: build (with XCode)
     Depending on your XCODE version the Toolset will be automatically chosen
 ---------------------- Current Python version: Python 3.13.0 -------------------- 

 

This is in case the sources have changed at the moment of launch, then an update will occur and the second banner will be useful. You can disable the update at launch and the second banner will disappear. I can do this for those who want, updates will remain available by pressing a key.

[matxpa]

16 hours ago, Slice said:

The script buildme is broken. Use xbuildme. One nonsense is green text 🙃

@Slice

Hi

Spoiler

 

@MakAsrock

Hi

xbuildme (line 87 COL_RESET not initialized is null) commit176a61b (or 683eeae from PR)

so you should initialize the COL_RESET variable, that would be better (for ex. as COL_RESET="\033[0m")

 

Regards

[naiclub]

On 9/10/2025 at 6:24 AM, Anto65 said:

 

You like the new " launcher app " ?

try this if you want https://github.com/ggkevinnnn/LaunchNow/releases/tag/v1.3.0   no need any patch , it s just a app

Spoiler

Very excellent

[Max.1974]

@Matgen84 my brother, it's running smoothly now  

 

 

 

Edited September 11, 2025 by Max.1974

[Matgen84]

23 hours ago, Max.1974 said:

@Matgen84 my brother, it's running smoothly now 

 

 

 

@Max.1974 where I can find v11 ?

[Max.1974]

15 hours ago, Matgen84 said:

 

@Max.1974 where I can find v11 ?

 

Her my friend  

 

Clover Compiler Builder v12.2 fix python 

 

 

 

 

 

 

 

Edited September 13, 2025 by Max.1974

[Max.1974]

For me working fine with Anaconda Python but you can choose whatever python you want   

[Matgen84]

7 hours ago, Max.1974 said:

 

Her my friend  

 

Clover Compiler Builder v12.2 fix python 

 

 

 

 

 

 

 

 

Hi @Max.1974 Thanks for your link. Is Clover Compiler Builder v12.2  arm64 version compatible with Intel ?

[Max.1974]

6 hours ago, Matgen84 said:

 

Hi @Max.1974 Thanks for your link. Is Clover Compiler Builder v12.2  arm64 version compatible with Intel ?

 

Yes my friend, is native shell script tools  

[MakAsrock]

Finished cosmetic changes to buildme. Removed interface demo at startup. Expanded autobuild commands from one ("" ci) to two (""xci):
# Main
clone_OpenCorePkg
set -e
if [[ "$2" == "ci" ]]; then
makeRelease
buildPkg
buildIso
makeV2
elif [[ "$2" == "xci" ]]; then
makeReleaseXC
buildPkg
buildIso
makeV2
else
menu
fi

Edited September 14, 2025 by MakAsrock

[MakAsrock]

On 9/11/2025 at 1:17 PM, matxpa said:

@Slice

Hi

  Reveal hidden contents

 

@MakAsrock

Hi

xbuildme (line 87 COL_RESET not initialized is null) commit176a61b (or 683eeae from PR)

so you should initialize the COL_RESET variable, that would be better (for ex. as COL_RESET="\033[0m")

 

Regards

In today's revision, there should be no more cosmetic flaws.

[Alpha22]

 

@MakAsrock compiling from scratch would seem faster

 

Spoiler

 

Thank you and well done

[MakAsrock]

4 hours ago, Alpha22 said:

 

@MakAsrock compiling from scratch would seem faster

 

  Hide contents

 

Thank you and well done

Будь ласка! You are welcome!

Edited September 15, 2025 by MakAsrock

[MakAsrock]

Xcode26 arrived over the air today. I did an emergency buildme update to work around the issue temporarily.
As far as I understand the logs, in the Slice branch the compilation has been ending with an error for 4 days already.

 

Edited September 16, 2025 by MakAsrock

[Max.1974]

@MakAsrock How’s it going? edited: I see now 🍀 

Have you installed the new CLT yet? Here compiled normally since yesterday 

 

 

 

Edited September 17, 2025 by Max.1974

[MakAsrock]

7 hours ago, Max.1974 said:

@MakAsrock How’s it going? edited: I see now 🍀 

Have you installed the new CLT yet? Here compiled normally since yesterday 

 

 

 

I only replaced CLOVERX64.efi with a new one, just to test it. The rest is from the previous copy. Only I have a newer build.I haven't used the installer for several years.

 

bdmesglog.txt.zip

Edited September 17, 2025 by MakAsrock