Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

2 hours ago, Matgen84 said:

 

I build a custom Clover PKG with a custom script. The best way to build latest commit is:

  • download or git clone from repo
  • from the directory, run ./buildme XCODE8 from Terminal

By default, Buildme use GCC53 toolchain.

 

Well...that's the thing.

 

I tried with both ./buildme XCODE8 (which I was using for a long time) aaand without. And I had the same issue with both.

 

Also, apparently there have been a few more commits and now I don't get the error above anymore. But I do get stuck at translating resources.

 

========= Translating Resources ========
/Users/jimmy/src/CloverBootloader/toolchain
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
XCode version too old. Not extracting locale strings from source XIB file
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
XCode version too old. Not extracting locale strings from source XIB file
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
XCode version too old. Don't extracting locale strings from source files
stat: ../CloverUpdater/CloverUpdater.strings: stat: No such file or directory
stat: ../CloverPrefpane/CloverPrefpane.strings: stat: No such file or directory
po4a-clover.cfg:12: The '../CloverUpdater/CloverUpdater.strings' master file does not exist.

make: *** [pkg] Error 2

 

I'm guessing if you rebuild your work directory you might have it too. :)

Link to comment
Share on other sites

14 minutes ago, arsradu said:

 

Well...that's the thing.

 

I tried with both ./buildme XCODE8 (which I was using for a long time) aaand without. And I had the same issue with both.

 

Also, apparently there have been a few more commits and now I don't get the error above anymore. But I do get stuck at translating resources.

 


========= Translating Resources ========
/Users/jimmy/src/CloverBootloader/toolchain
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
XCode version too old. Not extracting locale strings from source XIB file
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
XCode version too old. Not extracting locale strings from source XIB file
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
XCode version too old. Don't extracting locale strings from source files
stat: ../CloverUpdater/CloverUpdater.strings: stat: No such file or directory
stat: ../CloverPrefpane/CloverPrefpane.strings: stat: No such file or directory
po4a-clover.cfg:12: The '../CloverUpdater/CloverUpdater.strings' master file does not exist.

make: *** [pkg] Error 2

 

I'm guessing if you rebuild your work directory you might have it too. :)

 

I can build on a existing folder as I says before. I don't test from scratch. 

 

Why you got a toolchain subdirectory src/CloverBootloader/toolchain?

Link to comment
Share on other sites

1 minute ago, Matgen84 said:

 

Why you got a toolchain subdirectory src/CloverBootloader/toolchain?

Because is the default toolchain path. ifyou delete the src folder (mine is just ~/CloverBootloader) then every things will be self contained. 

Link to comment
Share on other sites

40 minutes ago, vector sigma said:

I guess you forgot to set the command line tools path:

 

..and BaseTools needs to be rebuilt

 

Your guess is...not wrong. :)

 

For some reason, I thought that was already set. But looks like it wasn't.

 

It's all good now, and it worked with GCC53 (without "XCODE8"), as well.

 

Thank you!

 

Update: theme issue still occurs with r5105 (dfd649dd5).

Edited by arsradu
  • Like 2
Link to comment
Share on other sites

16 minutes ago, arsradu said:

Update: theme issue still occurs with r5105 (dfd649dd5).

 

You can optimize your theme via new function in Clover.app called "Optimize" button.

  • Like 1
Link to comment
Share on other sites

Hi @Slice

 

Is it possible to put commit number in the installer log. It will be useful, I think. Thanks.

 

Clover EFI installer log - Fri Mar 13 18:10:18 CET 2020
Installer version: r5105 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         1000.0 GB  disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk1
   1:                        EFI NO NAME                 353.4 MB   disk1s1
   2:         Microsoft Reserved                         16.8 MB    disk1s2
   3:       Microsoft Basic Data Win10                   2.0 TB     disk1s3
   4:           Windows Recovery                         516.9 MB   disk1s4

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1000.0 GB  disk2
                                 Physical Store disk0s2
   1:                APFS Volume Mojave                  545.2 GB   disk2s1
   2:                APFS Volume Preboot                 24.1 MB    disk2s2
   3:                APFS Volume Recovery                510.4 MB   disk2s3
   4:                APFS Volume VM                      8.6 GB     disk2s4

 

Link to comment
Share on other sites

6 minutes ago, Matgen84 said:

 

You can optimize your theme via new function in Clover.app called "Optimize" button.

Well, that worked. :) 

 

It doesn't give you a visual feedback when it's done "optimising", only an audible one. If you have your speakers on or your headphones. Maybe a pop-up or notification or something would be nice. Also, I'm guessing this doesn't happen with all the themes, right? It's probably only with the older ones.

 

In my case, I'm using and I absolutely love Minimalism. Simple black and white theme. I keep coming back to it over and over again.

 

Anyway, looks like the optimise button did its job. Thank you!

  • Like 1
Link to comment
Share on other sites

@Slice on your recent commit on "rEFIt_UEFI/refit/lib.cpp", maybe you need a small fix?

 

  CHAR8 strLog[50];

  ...

  for (INTN i = 0; i < len; i++) {
    strLog[i + end] = '=';
  }
  //strLog[50] = '\0';
  strLog[49] = '\0';
  DebugLog (1, "%a\n", strLog);
 

otherwise - FYI everything seems to work again with r5105. 

 

Edited by tluck
  • Like 1
Link to comment
Share on other sites

57 minutes ago, tluck said:

@Slice on your recent commit on "rEFIt_UEFI/refit/lib.cpp", maybe you need a small fix?

 

  CHAR8 strLog[50];

  ...

  for (INTN i = 0; i < len; i++) {
    strLog[i + end] = '=';
  }
  //strLog[50] = '\0';
  strLog[49] = '\0';
  DebugLog (1, "%a\n", strLog);
 

otherwise - FYI everything seems to work again with r5105. 

 

Thanks! I am inattentive today.

Link to comment
Share on other sites

Hi @Slice

 

Yesterday, I update r5105 48b175 to r5105 5ed385d, without reboot. This morning, I have no Clover GUI only black screen.

 

Do you think is a Clover problem or macOS issue? I rebuild several time kernel cache from a working USB stick (5104), don't works. There is a message Error Kernel cache 0x09.

 

I've also reinstall macOS Mojave from Recovery partition after booting on a USB stick (r5104).

 

When I succeeded to rollback to r5105 48b175 : all works. 

I don't understand what's happen.

 

1.jpg

Edited by Matgen84
  • Thanks 1
Link to comment
Share on other sites

Hi 

 

I can't build latest commit r5105 7461b02.

 

Spoiler

[CPP] FloatLib
[CPP] VectorGraphics
/Users/mathieu/src/CloverBootloader/rEFIt_UEFI/libeg/XImage.cpp:500:29: error: cannot pass object of non-trivial type 'const XStringW' through variadic function; call will abort at runtime [-Wnon-pod-varargs]
    DBG("%s not decoded\n", FileName);
                            ^
1 error generated.
make: *** [/Users/mathieu/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/libeg/XImage.obj] Error 1


build.py...
 : error 7000: Failed to execute command
    make tbuild [/Users/mathieu/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
    /Users/mathieu/src/CloverBootloader/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 17:25:54, Mar.18 2020

 

Link to comment
Share on other sites

4 hours ago, CMMChris said:

10.15.4 Beta 6 doesn't boot. Possibly broken kext injection?

 

Works fine for me... But we have some hardware differences (not sure how important they are in this case), and I'm using Clover r5105 (dfd649dd5). So not the latest build from sources, but also not the official r5105 from a week ago either. It's somewhere in the middle.

 

You can find it attached if you wanna give it a try.

Clover_r5105.pkg.zip

Edited by arsradu
  • Like 2
Link to comment
Share on other sites

11 hours ago, Matgen84 said:

Hi 

 

I can't build latest commit r5105 7461b02.

 

  Hide contents

[CPP] FloatLib
[CPP] VectorGraphics
/Users/mathieu/src/CloverBootloader/rEFIt_UEFI/libeg/XImage.cpp:500:29: error: cannot pass object of non-trivial type 'const XStringW' through variadic function; call will abort at runtime [-Wnon-pod-varargs]
    DBG("%s not decoded\n", FileName);
                            ^
1 error generated.
make: *** [/Users/mathieu/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/libeg/XImage.obj] Error 1


build.py...
 : error 7000: Failed to execute command
    make tbuild [/Users/mathieu/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
    /Users/mathieu/src/CloverBootloader/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 17:25:54, Mar.18 2020

 

There must be DBG("%s not decoded\n", FileName.data());

 

committed

  • Thanks 1
Link to comment
Share on other sites

@Slice

I think there was an old mistake in this commit, regarding mask handling for Kernel patches / Boot patches. Seems to me that NrKexts was used by mistake instead of NrKernels and NrBoots.

On one computer, it caused for me hang before Clover GUI even loaded, due to attempt to copy to unallocated location.

But I think this might have also caused problems with kexts/kernel patches in other cases.

Please check my commit with the correction for this and look if it seems right to you.

 

Edited by Pene
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

6 hours ago, Pene said:

Please check my commit with the correction for this and look if it seems right to you.

 

 

Clover r5105_4d07a7376 working well here, both UEFI & BIOS boot... 

 

screenshot0.thumb.png.207a29ab1afbaa6c2283bb8f5b60bb75.png

 

Like @Matgen84, I was getting black screen/no GUI on UEFI boot for r5105_5ed385d (before your commits).

 

Attached is working latest Clover_r5106.pkg_23ba4b218.

 

Edited by fusion71au
Attach r5106_23ba4b218
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

10 hours ago, Pene said:

@Slice

I think there was an old mistake in this commit, regarding mask handling for Kernel patches / Boot patches. Seems to me that NrKexts was used by mistake instead of NrKernels and NrBoots.

On one computer, it caused for me hang before Clover GUI even loaded, due to attempt to copy to unallocated location.

But I think this might have also caused problems with kexts/kernel patches in other cases.

Please check my commit with the correction for this and look if it seems right to you.

 

Respect Pene!

It is the key bug. Thank you for notice.

  • Like 3
Link to comment
Share on other sites

On 3/10/2020 at 11:17 PM, vector sigma said:

CloverV2 is the zipped CloverV2 directory. The other one is the pkg + md5 which in case is compressed with the loseless compression algo decided by pkgutil... which is way better than zip... why the difference.

I think we should rename Clover-r5XXX.zip to something more understandable like  Clover-r5XXX.pkg.zip.

I just don't know if it will influence on Update process.

  • Like 2
Link to comment
Share on other sites

3 hours ago, Slice said:

I think we should rename Clover-r5XXX.zip to something more understandable like  Clover-r5XXX.pkg.zip.

I just don't know if it will influence on Update process.

Hi Slice, you firstly update the folder with the package and the md5 as "Clover_r5105.zip" and later I fixed the release by uploading just the pkg (Clover_r5105.pkg).

Apparently you did the same for r5106 while you never did this for all old releases...why?

5104.png.13370b913cf2122fce73cbd2a5049aeb.png

 

VS

 

5106.png.7708258065bb59fbab63068f6db93406.png

 

You should upload just Clover_r5106.pkg

Edited by vector sigma
Link to comment
Share on other sites

Hi guys,

 

Should the Clover app update work from within the Clover App itself...? Cause it kinda didn't for me... It showed 5106 as available. I clicked Download (or Get or whatever button it was), it showed a progress bar underneath...but...nothing else. No pkg on the Desktop or anywhere else. No installer pop-up... It's like it never did anything. :))

 

I downloaded Clover.app_v1.16_r5106.pkg.zip manually, which also made the button to "Install 5106" appear. It was always "Install 5105" before that...

 

Maybe it's just me though. I'm not too familiar with the newer releases of the Clover app. One thing I noticed though, the installation itself is super fast.

 

I don't have CloverUpdater anymore. So...I don't know if updating from that section works now.

Link to comment
Share on other sites

×
×
  • Create New...