Jump to content
30960 posts in this topic

Recommended Posts

Found a logical error that in certain cases could lead to a crash in the copying process. I don't know why the check for the folder existence was needed if mkdir -p is used anyway? But just in case, I corrected it and left it. Inserted the missing (!) in this block:

Spoiler
BLC() {
if [[ ! -d "${CLOVERROOT}/CloverPackage/BootLoaderChooser" ]]; then
  mkdir -p "${CLOVERROOT}/CloverPackage/BootLoaderChooser"
fi
curl -sLq https://github.com/jief666/BootloaderChooser/releases/download/1.4/BootX64.efi > "${CLOVERROOT}/CloverPackage/BootLoaderChooser/BootX64.efi"
chmod 775 "${CLOVERROOT}/CloverPackage/BootLoaderChooser/BootX64.efi"
xattr -d com.apple.quarantine "${CLOVERROOT}/CloverPackage/BootLoaderChooser/BootX64.efi" 2>/dev/null || true
}

 

 

Edited by MakAsrock
  • Like 2
On 8/28/2025 at 4:38 PM, Max.1974 said:

Hi @Matgen84 

 

I think try fix clean git clone folder before, and fix errors about it. Im used run 2 build all default toolchain, compile everything. ;) 

 

Im test 3 and 7, we get errors  because need run option compiler first, so choose number 1) or  2) from menu. I  adjust for not delete folder if exist 

 

Here in English my friend with or without git clone repo in $Home/ Just click twice and run (if you wanted in French tell me) 

 

image.png.2e306c06f1ea59d007e0216955791684.png image.png.3f8e23efff5981ff1b82dcc67edd30bf.png

image.png.1e47b24651b6036747715da2d100d365.png image.png.4cd35cca8c0b707e74cdc95d1495e96d.png

 

 

 

 

Fixed ask about delete or not git clone Clover folder 

 

image.thumb.png.8c029d2b093b74b26ac99021561bc88f.png

 

 

Clover Compiler Builder - English - ASK II.zip 3.54 MB · 7 downloads

 

 

 

Added an important patch to the script for the Slice Published builder.

Spoiler

Look:
 

# Patch buildme if necessary
if [ -f buildme ]; then
[ ! -f buildme.backup ] && cp buildme buildme.backup
# Fix tee problem
  if grep -qE 'make[[:space:]]+pkg[[:space:]]*>[[:space:]]*mpkg\.log' buildme; then
  sed -i.bak 's/make[[:space:]]\+pkg[[:space:]]*>[[:space:]]*mpkg\.log/make pkg | tee mpkg.log/g' buildme
    if grep -qE 'read[[:space:]]\+~\/Applications/Xcode.app' buildme; then
    sed -i 's/read[[:space:]]\+\/Applications/Xcode.app/g' buildme
    chmod +x buildme
    fi
  fi
fi

 

 

  • Like 2
  • Thanks 1
1 hour ago, MakAsrock said:

Added an important patch to the script for the Slice Published builder.

  Hide contents

Look:
 

# Patch buildme if necessary
if [ -f buildme ]; then
[ ! -f buildme.backup ] && cp buildme buildme.backup
# Fix tee problem
  if grep -qE 'make[[:space:]]+pkg[[:space:]]*>[[:space:]]*mpkg\.log' buildme; then
  sed -i.bak 's/make[[:space:]]\+pkg[[:space:]]*>[[:space:]]*mpkg\.log/make pkg | tee mpkg.log/g' buildme
    if grep -qE 'read[[:space:]]\+~\/Applications/Xcode.app' buildme; then
    sed -i 's/read[[:space:]]\+\/Applications/Xcode.app/g' buildme
    chmod +x buildme
    fi
  fi
fi

 

 

 

 

Apply your choice about patch: v4

Captura de Tela 2025-08-30 às 20.31.43.png

Added Information:

 

Option 1 (Local Patch):

  • Fixes the tee issue (shows real-time output)

  • Removes problematic Xcode line

  • Uses Clover’s original buildme

 

Option 2 (Download):

 

  • Downloads pre-patched version from YBronst/Asrock-Z690-PG-Reptide

  • Completely replaces the native buildme

 

Option 3 (Native):

  • Uses original buildme without fixes

 

 

 

Edited by Max.1974
  • Like 2

Why not remove unenessary tools inside this script

Every body can use this tool without the script option

 

image.png.6d4b8ef38a654c4f091e7635df49ad2a.png

 

Edited by chris1111
  • Like 1
  • Thanks 1
8 minutes ago, chris1111 said:

Why not remove unenessary tools inside this script

Every body can use this tool without the script option

 

 

if you remove this maybe I will commit the correct buildme

 

Hi @chris1111 my friend, the original code was left unchanged and it still works fine here. However, we can review and refine it together if needed, and you think is better. ;) 

  • Like 2

Clover Builder Clean v5 - Major Improvements and Optimizations

What Was Removed (Problematic Features)

  • All external tool download options – Eliminated dependencies on external repositories that were causing build failures

  • External tool dependencies – Removed downloads for CloverConfigPlistValidator, Hackintool, BitmaskDecode, MaciASL, dmidecode, IOReg-Devices, NativeDisplayBrightness, SSDTTime, USBMap, Xiasl, CsrDecode, gibMacOS, and mountR/W

  • Complex menu systems – Simplified the interface to focus on core functionality

  • Network-dependent operations – Eliminated potential points of failure from external downloads

 

Clover Builder Clean v5.zip

 

 

clover-leaf4-png1.thumb.png.ad4072121feeba2550d8f08896653cb9.png

 

:plane: 

  • Like 7
  • Confused 1
6 hours ago, Max.1974 said:

Clover Builder Clean v5 - Major Improvements and Optimizations

What Was Removed (Problematic Features)

  • All external tool download options – Eliminated dependencies on external repositories that were causing build failures

  • External tool dependencies – Removed downloads for CloverConfigPlistValidator, Hackintool, BitmaskDecode, MaciASL, dmidecode, IOReg-Devices, NativeDisplayBrightness, SSDTTime, USBMap, Xiasl, CsrDecode, gibMacOS, and mountR/W

  • Complex menu systems – Simplified the interface to focus on core functionality

  • Network-dependent operations – Eliminated potential points of failure from external downloads

 

Clover Builder Clean v5.zip 1.86 MB · 9 downloads

 

 

clover-leaf4-png1.thumb.png.ad4072121feeba2550d8f08896653cb9.png

 

:plane: 

And now open Terminal and  enter the command:   /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)" when asked, enter the password. Once finished, enter another command: sudo rm -rf /opt/homebrew/ 😡 I hate it when non-Apple products are installed on my system without asking! Useless tool! My Clover is not in src but in Developer. That's why it's not correct to set the working directory: WORKDIR="$HOME/src" 🫡

Edited by MakAsrock
  • Like 1

Native git clone is in src. I made many options. Use what is better for you. This tools is original from normally users installer. And just update python. If you not want can use another options or your own code. Not remove without ask. You can change code sh above. I’m share with you. Your angry is not justify. 

Im share with Slice too. He’s thankful for give another options for users. 

And I gave many options to choose before. This is clean version without your buildme. 

Left two python installer cause two windows of twice python versions. Old and new. I was thinking you are knowledge about it. 

Edited by Max.1974
  • Like 1
1 hour ago, Max.1974 said:

Native git clone is in src. I made many options. Use what is better for you. This tools is original from normally users installer. And just update python. If you not want can use another options or your own code. Not remove without ask. You can change code sh above. I’m share with you. Your angry is not justify. 

Im share with Slice too. He’s thankful for give another options for users. 

And I gave many options to choose before. This is clean version without your buildme. 

Left two python installer cause two windows of twice python versions. Old and new. I was thinking you are knowledge about it. 

Yes, I know. But I don't like what clutters up my almost native system. All the tools, I can download and install myself.

1 hour ago, Max.1974 said:

Just change line to put your clover where you want. 

Ok, I have already met those who wish and removed the tools section from the main build. here is the edited tool. It works fine and I'll add it to github after final testing. 😉

Снимок экрана 2025-08-31 в 12.29.28.jpg

Clover Compiler Builder.zip

Снимок экрана 2025-08-31 в 12.39.08.jpg

mpkg.log.zip

Edited by MakAsrock
  • Like 3
15 hours ago, Max.1974 said:

 - Major Improvements and Optimizations

What Was Removed (Problematic Features)

  • All external tool download options – Eliminated dependencies on external repositories that were causing build failures

  • External tool dependencies – Removed downloads for CloverConfigPlistValidator, Hackintool, BitmaskDecode, MaciASL, dmidecode, IOReg-Devices, NativeDisplayBrightness, SSDTTime, USBMap, Xiasl, CsrDecode, gibMacOS, and mountR/W

  • Complex menu systems – Simplified the interface to focus on core functionality

  • Network-dependent operations – Eliminated potential points of failure from external downloads

 

Clover Builder Clean v5.zip 1.86 MB · 14 downloads

 

 

clover-leaf4-png1.thumb.png.ad4072121feeba2550d8f08896653cb9.png

 

:plane: 

@Max.1974 I tried Clover Builder Clean v5 but it fails to compile, can you check it?

I am using macOS Thaoe beta 8 and Xcode Version 26.0 beta 6

Output di Terminale salvato.txt.zip Output di Terminale salvato01.txt.zip

Edited by Alpha22
  • Like 1

Here the tests of some fixes maybe you can try use now this v6 

 

 

 

Spoiler

CLOVER BUILDER v6 - EXECUTION RESULTS
=====================================

VERSION v6 EXECUTION RESULTS:

1. SUCCESSFUL COMPILATION:
   - Build completed in 44 seconds
   - No compilation errors
   - All patches applied correctly

2. GENERATED FILES:
    CloverX64-RELEASE_GCC151-20250827141148-2fa933e-dirty.efi
    Clover_r5163.pkg (5.8 MB)
    Clover-5163-X64.iso
    CloverISO-5163.tar.lzma

3. SUCCESSFULLY APPLIED PATCHES:
    Multi-line comment fix (line 59) - RESOLVED
    Unused variable fix (line 231) - RESOLVED  
    GCC151 configuration - APPLIED
    BaseTools compilation - SUCCESS
    Buildme patching - WORKING

4. COMPLETE PROCESS:
   - Automatic setup of all dependencies
   - Corrections applied to source code
   - Clean compilation without errors
   - Package and ISO generation
   - Interactive menu working perfectly

🎯 FINAL CONCLUSION:

Version v6 is 100% functional and resolves exactly the problems the user faced:
- No compilation errors
- Robust patches applied
- Complete and functional build
- Optimized compilation time

Version v6 is ready for delivery and should completely resolve the user's compilation problems!

=====================================
BUILD DETAILS:
- Build start time: 14:43:52, Aug.31 2025
- Build end time: 14:44:34, Aug.31 2025
- Build total time: 00:00:42
- Toolchain: GCC151
- Architecture: X64
- Build target: RELEASE
- Python version: Python 3.13.7

=====================================
PATCHES APPLIED:
1. Enhanced Multi-line Comment Fix (AcpiParser.h line 59)
2. Enhanced Unused Variable Fix (AcpiParser.c line 231)
3. Enhanced GCC151 Configuration (multiple safety flags)
4. Enhanced Buildme Patching (real-time output)
5. Enhanced Verification of All Fixes

=====================================
COMPILATION STATUS:
- BaseTools: SUCCESS
- OpenCorePkg: SUCCESS
- Clover: SUCCESS
- Package Generation: SUCCESS
- ISO Generation: SUCCESS
- CloverV2: SUCCESS

=====================================
FILES CREATED:
- CloverX64-RELEASE_GCC151-20250827141148-2fa933e-dirty.efi
- Clover_r5163.pkg (5.8 MB)
- Clover-5163-X64.iso
- CloverISO-5163.tar.lzma
- Various driver files (.efi)
- Boot sector files

=====================================
VERSION v6 ENHANCEMENTS:
✓ Enhanced multi-line comment fix (more robust)
✓ Enhanced unused variable fix (more reliable)
✓ Enhanced GCC151 configuration (multiple safety flags)
✓ Enhanced verification of all fixes
✓ All external tool download options removed
✓ No more dependency on external repositories
✓ Focus on core Clover compilation
✓ Cleaner, more reliable build process

=====================================
STATUS: READY FOR DELIVERY
The user can now use this version to successfully compile Clover without the previous compilation errors.

 

 

 

CapturadeTela2025-08-31as14_50_36.png.ee617fdbd9171dccc4921059234ee97d.png

Clover_Builder_v6_Full_Terminal_Output.txt.zip

 

Log

 

Clover Builder Compiler v6 EN

 

Clover Builder v6.zip

 

 

 

icon6.thumb.png.d67af6d3a40fbd85a044d9d1c2519583.png

 

 

 

  • Like 2

@Max.1974 @MakAsrock I look to the buildme here I see good improvement and correctif

Good Work 👍🏻

 

But I don't think it's a good idea to add clover patches in the buildme script

because clover patches must be added to the source and approved by Slice

 

All these fixes mentioned must be easely fixed at the Clover source

# CRITICAL FIX 1: Fix problematic source code

# Fix unused variable on line 231

# CRITICAL FIX 2: Configure GCC151 for error-free build

# Fix GCC151 configuration

  • Like 3
18 minutes ago, chris1111 said:

@Max.1974 @MakAsrock I look to the buildme here I see good improvement and correctif

Good Work 👍🏻

 

But I don't think it's a good idea to add clover patches in the buildme script

because clover patches must be added to the source and approved by Slice

 

All these fixes mentioned must be easely fixed at the Clover source

# CRITICAL FIX 1: Fix problematic source code

# Fix unused variable on line 231

# CRITICAL FIX 2: Configure GCC151 for error-free build

# Fix GCC151 configuration

 

Hi @chris1111 my friend, 

 

The buildme from MakAsrock, created by him, is under Slice’s supervision at AppleLife.RU.

My patch only highlights the errors and tries to work around them, and I spoke with Slice and he is happy with the help being given to users. Apparently, I am not changing the code, only adjusting it so the system can compile.

MakAsrock is in contact with Slice all the time. Here on Insanely, my fast internet isn’t working, and I don’t know why — I guess the channel owners aren’t updating the speeds, not sure.

As far as I can help, I’m glad to, Chris, and you can help us by shedding some light, but I’m not up to date with the work on buildme. I create patcher using original buildme from Clover github. 

 

 

Clover discussion Apple Life RU p. 1572

 

Spoiler

CapturadeTela2025-08-31s20_06_56.thumb.png.f6caba8da7f30e88983f25b01f6dd1f0.png

 

Edited by Max.1974
  • Like 4
9 hours ago, Max.1974 said:

Here the tests of some fixes maybe you can try use now this v6 

 

 

 

  Reveal hidden contents

CLOVER BUILDER v6 - EXECUTION RESULTS
=====================================

VERSION v6 EXECUTION RESULTS:

1. SUCCESSFUL COMPILATION:
   - Build completed in 44 seconds
   - No compilation errors
   - All patches applied correctly

2. GENERATED FILES:
    CloverX64-RELEASE_GCC151-20250827141148-2fa933e-dirty.efi
    Clover_r5163.pkg (5.8 MB)
    Clover-5163-X64.iso
    CloverISO-5163.tar.lzma

3. SUCCESSFULLY APPLIED PATCHES:
    Multi-line comment fix (line 59) - RESOLVED
    Unused variable fix (line 231) - RESOLVED  
    GCC151 configuration - APPLIED
    BaseTools compilation - SUCCESS
    Buildme patching - WORKING

4. COMPLETE PROCESS:
   - Automatic setup of all dependencies
   - Corrections applied to source code
   - Clean compilation without errors
   - Package and ISO generation
   - Interactive menu working perfectly

🎯 FINAL CONCLUSION:

Version v6 is 100% functional and resolves exactly the problems the user faced:
- No compilation errors
- Robust patches applied
- Complete and functional build
- Optimized compilation time

Version v6 is ready for delivery and should completely resolve the user's compilation problems!

=====================================
BUILD DETAILS:
- Build start time: 14:43:52, Aug.31 2025
- Build end time: 14:44:34, Aug.31 2025
- Build total time: 00:00:42
- Toolchain: GCC151
- Architecture: X64
- Build target: RELEASE
- Python version: Python 3.13.7

=====================================
PATCHES APPLIED:
1. Enhanced Multi-line Comment Fix (AcpiParser.h line 59)
2. Enhanced Unused Variable Fix (AcpiParser.c line 231)
3. Enhanced GCC151 Configuration (multiple safety flags)
4. Enhanced Buildme Patching (real-time output)
5. Enhanced Verification of All Fixes

=====================================
COMPILATION STATUS:
- BaseTools: SUCCESS
- OpenCorePkg: SUCCESS
- Clover: SUCCESS
- Package Generation: SUCCESS
- ISO Generation: SUCCESS
- CloverV2: SUCCESS

=====================================
FILES CREATED:
- CloverX64-RELEASE_GCC151-20250827141148-2fa933e-dirty.efi
- Clover_r5163.pkg (5.8 MB)
- Clover-5163-X64.iso
- CloverISO-5163.tar.lzma
- Various driver files (.efi)
- Boot sector files

=====================================
VERSION v6 ENHANCEMENTS:
✓ Enhanced multi-line comment fix (more robust)
✓ Enhanced unused variable fix (more reliable)
✓ Enhanced GCC151 configuration (multiple safety flags)
✓ Enhanced verification of all fixes
✓ All external tool download options removed
✓ No more dependency on external repositories
✓ Focus on core Clover compilation
✓ Cleaner, more reliable build process

=====================================
STATUS: READY FOR DELIVERY
The user can now use this version to successfully compile Clover without the previous compilation errors.

 

 

 

CapturadeTela2025-08-31as14_50_36.png.ee617fdbd9171dccc4921059234ee97d.png

Clover_Builder_v6_Full_Terminal_Output.txt.zip 6.31 kB · 2 downloads

 

Log

 

Clover Builder Compiler v6 EN

 

Clover Builder v6.zip 1.75 MB · 5 downloads

 

 

 

icon6.thumb.png.d67af6d3a40fbd85a044d9d1c2519583.png

 

 

 

 

@Max.1974 

I tried Clover Builder Clean v6 but it fails to compile, can you check it?

I am using macOS Thaoe beta 8 and Xcode Version 26.0 beta 6

 

Output di Terminale salvato01.txt.zip Output di Terminale salvato.txt.zip

  • Like 2
4 hours ago, Max.1974 said:

 

Hi @chris1111 my friend, 

 

The buildme from MakAsrock, created by him, is under Slice’s supervision at AppleLife.RU.

My patch only highlights the errors and tries to work around them, and I spoke with Slice and he is happy with the help being given to users. Apparently, I am not changing the code, only adjusting it so the system can compile.

MakAsrock is in contact with Slice all the time. Here on Insanely, my fast internet isn’t working, and I don’t know why — I guess the channel owners aren’t updating the speeds, not sure.

As far as I can help, I’m glad to, Chris, and you can help us by shedding some light, but I’m not up to date with the work on buildme. I create patcher using original buildme from Clover github. 

 

 

Clover discussion Apple Life RU p. 1572

 

  Reveal hidden contents

CapturadeTela2025-08-31s20_06_56.thumb.png.f6caba8da7f30e88983f25b01f6dd1f0.png

 

There is a great idea: Make buldme with utilities, pbuildme with patches and without utilities and finally a completely clean version of cbuildme. Only I always had a problem writing descriptions.

  • Like 2
1 hour ago, MakAsrock said:

There is a great idea: Make buldme with utilities, pbuildme with patches and without utilities and finally a completely clean version of cbuildme. Only I always had a problem writing descriptions.

Done. They are on git hub. 🙂

Edited by MakAsrock
  • Like 3
3 hours ago, Alpha22 said:

 

@Max.1974 

I tried Clover Builder Clean v6 but it fails to compile, can you check it?

I am using macOS Thaoe beta 8 and Xcode Version 26.0 beta 6

 

Output di Terminale salvato01.txt.zip 2.27 kB · 0 downloads Output di Terminale salvato.txt.zip 11.07 kB · 1 download

 

I honestly feel very frustrated for not being able to figure this out. I analyzed six logs and the same system here with very similar hardware was already showing problems. But I want to make it clear that it’s not necessary to compile on your machine — this isn’t like a kext or other programs. Clover is in a different situation: the compilation from GitHub is superior to what we can build ourselves. No matter how advanced the hardware is, we don’t have control over what is or isn’t installed on your system.

 

If it’s a clean installation, let the tools chosen by the bash script install themselves. The Clover build available for download in the actions folder is much more advanced and comes with very high-end tools.

So I really can’t analyze it unless I know exactly how you installed it. And I’m sorry — honestly, I wouldn’t be able to help without you telling me the types of installers you used, the Python version, where you installed Homebrew, and whether you are replacing the build or not. Please test these versions. But they have already shown errors on other machines, maybe you can try another versions. Would you like to test? 

 

 

 

 

Clover Builder v8.zip

 

Fixes for some machines:

 

REPLY=""
SUDO_PASSWORD=""

 

if [ ! -d "$REPO_DIR/.git" ] || [ "${REPLY:-}" = "y" ]; then

 

if [ -n "$SUDO_PASSWORD" ] && echo "$SUDO_PASSWORD" | sudo -S ... 

 

"unbound variable" in line 279

 

 

 

Edited by Max.1974
  • Like 2
  • Thanks 1
2 hours ago, MakAsrock said:

There is a great idea: Make buldme with utilities, pbuildme with patches and without utilities and finally a completely clean version of cbuildme. Only I always had a problem writing descriptions.

 

I believe your code has potential, and since you have Slice’s support, I’m sure you’ll find a middle ground. What I intended was to help, not to create a script that causes problems — in the Hackintosh scenario we don’t have a guarantee of perfection. It’s not a strict logic, and I will pause until the errors found are fixed, as Slice told you.

  • Like 4
5 hours ago, Max.1974 said:

So I really can’t analyze it unless I know exactly how you installed it. And I’m sorry — honestly, I wouldn’t be able to help without you telling me the types of installers you used, the Python version, where you installed Homebrew, and whether you are replacing the build or not. Please test these versions. But they have already shown errors on other machines, maybe you can try another versions. Would you like to test? 

Of course I want to test the various versions

Clover Builder v8 application in disk/users/fabio

I use macOS Sequoia 15.6.1 with Xcode 16.4

 

first result v8.txt.zip

  • Like 1
  • Thanks 1
7 hours ago, Max.1974 said:

 

I believe your code has potential, and since you have Slice’s support, I’m sure you’ll find a middle ground. What I intended was to help, not to create a script that causes problems — in the Hackintosh scenario we don’t have a guarantee of perfection. It’s not a strict logic, and I will pause until the errors found are fixed, as Slice told you.

I found and fixed all the errors that were known to me at the time of Slice's publication and I am not against your wonderful work. I just don't want to install this wonderful Homebrew because it broke my Steam Wine for Gothic and since then I have not used it. This is not an attack, but a bug report. All versions of buildmt fixed that I wrote for Slice, a new clean version of cbuildme, a version with pbuildme patches and just a spare pbuildme are posted on my github.

  • Like 3
  • Thanks 1
21 minutes ago, MakAsrock said:

I found and fixed all the errors that were known to me at the time of Slice's publication and I am not against your wonderful work. I just don't want to install this wonderful Homebrew because it broke my Steam Wine for Gothic and since then I have not used it. This is not an attack, but a bug report. All versions of buildmt fixed that I wrote for Slice, a new clean version of cbuildme, a version with pbuildme patches and just a spare pbuildme are posted on my github.

@MakAsrock Your app works well with Tahoe.

  • Like 2
×
×
  • Create New...