Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Badruzeus
Badruzeus
Posted
Posted
19 minutes ago, chris1111 said:

No issue here light mode :rofl:



 

882741836_Capturedcranle2018-06-1212_03_22.png.a8e186db8621956f0d8d2b8fbc9cb20a.png

 

Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think.

Spoiler

What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL

 

Nvidia-Light-Dark.png

  • Like 1
arsradu
arsradu
Posted
Posted
Delete manually this folder and try again

Yep. Works fine with a fresh environment. Which means that most likely it is/was the fact that I “injected” the Clover sources into the environment instead of downloading them from svn that caused the issues.

 

Thank you so much for your feedback.

By the way, I’m not sure who should I be thanking for this, but building Clover using UDK2018 method is a LOT faster. It is probably also faster because it doesn’t build 32 bit versions anymore. But I don’t know, it just seems really, really fast now.

Well done!

 

arsradu
arsradu
Posted
Posted

Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense.

  

192-168-0-116:CloverPackage jimmy$ ./makepkg

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Don't extracting locale strings from source files

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$

Did anyone succeed to build Clover in Xcode 10 with this method?

Slice
Slice
Posted
Posted
1 hour ago, arsradu said:

Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense.

  


192-168-0-116:CloverPackage jimmy$ ./makepkg

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Not extracting locale strings from source XIB file
XCode version too old. Don't extracting locale strings from source files

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$

Did anyone succeed to build Clover in Xcode 10 with this method?

Show, please, output

xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'

Slice
Slice
Posted
Posted
5 hours ago, arsradu said:

 

Seems to be 1. 


192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$

 

I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5.

If anyone want old versions then welcome with your proposition how to do better way.

6 hours ago, arsradu said:

 

Seems to be 1. 


192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p'
1
192-168-0-116:~ jimmy$

 

Check, please

xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'

vector sigma
vector sigma
Posted
Posted
15 hours ago, Slice said:

fdisk440 should be revised or just excluded. It is compiled to 32bit which is no more supported.

There is a better way to install mbr0 sector sizeof 440 


dd if=/dev/disk0 count=1 bs=512 of=origMBR
cp origMBR newMBR
dd if=boot0 of=newMBR bs=1 count=440 conv=notrunc
dd if=newMBR of=/dev/disk0 count=1 bs=512

Someone can implement this into Clover Package? And completely exclude fdisk440.

 

EDITED.

Or /dev/rdisk0 ?

I'll do that tonight. Did you want to backup original boot sectors?

  • Like 1
arsradu
arsradu
Posted
Posted (edited)
2 hours ago, Slice said:

I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5.

If anyone want old versions then welcome with your proposition how to do better way.

Check, please

xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'

 

After updating sources, now it says "10". 

192-168-0-116:Clover jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p'
10
192-168-0-116:Clover jimmy$

Now, it says "updating 'en' strings"... But still fails in the same place: 

========= Translating Resources ========
/Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done

Building CloverUpdater application...
[XCODE]
Building CloverPrefpane preference...
** BUILD FAILED **

make: *** [CloverPrefpane] Error 65
192-168-0-116:CloverPackage jimmy$

 

Edited by arsradu
Badruzeus
Badruzeus
Posted
Posted (edited)

@Slice

Sorry, seems like I've missed important changes few months back.

What u mean with --Automatic choose "yourtheme" or "yourtheme@2x" if monitor is 2k or larger.--?

In my case, if there're "Lightness" and "Lightness256" themes on the repo already; do I need to rename Lightness256 to Lightness@2x (is exact naming)..?

"The criteria is ScreenHight > 1100", is this new value on theme.plist or u mean "DesignHeight" and Width will follow? Thanks.

Screenshot 31.png

Edited by Badruzeus
Badruzeus
Badruzeus
Posted
Posted
4 minutes ago, blackosx said:

Yeah. Slice posted a link to an example theme. I've not had time to look yet.

OK, just curious with "ScreenHeigh" and I have no bigger screen than 768 to test.

A question, can we use similar method to speed up CloverThemeManager sync process when updating just like this? Thanks.

kgp
kgp
Posted
Posted (edited)

@Slice, 

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

 

1289625263_Screenshot2018-06-13at09_07_13.thumb.png.920e579df01eaf5679c23d250efc99b1.png

Edited by KGP-iMacPro
Badruzeus
Badruzeus
Posted
Posted
14 minutes ago, KGP-iMacPro said:

@Slice, 

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

...

Where's the proof that your KP issue under 10.14 is caused by "Building 4538"..???

  • Like 1
arsradu
arsradu
Posted
Posted (edited)
15 hours ago, Badruzeus said:

 

Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think.

  Reveal hidden contents

What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL

 

Nvidia-Light-Dark.png

 

Hmm...where did you get this driver? :D

1 hour ago, KGP-iMacPro said:

@Slice, 

 

sorry yet another issue under 10.14, while the clover package builds totally fine under 10.13.5.

 

Warning!  Building 4538 can now cause a KP under 10.14 and can make your system totally irresponsive.  

 

1289625263_Screenshot2018-06-13at09_07_13.thumb.png.920e579df01eaf5679c23d250efc99b1.png

 

Have you tried building with UDK2018? I see you're still using edk2.

Also, no issues booting Mojave using Clover 4538. So...I'm guessing it might be something specific either to your config...or to your Clover build. It's just an idea. I could be wrong. But...as I said, doesn't happen to me.

If you want, you can give it a try.

Clover_v2.4k_r4538.pkg

Edited by arsradu
  • Haha 1
kgp
kgp
Posted
Posted
2 hours ago, Badruzeus said:

Where's the proof that your KP issue under 10.14 is caused by "Building 4538"..???

 

I got a KP while building 4538. It was the first and only one since one year. What else you want yo be proven? You should know yourself that it is impossible to provide proof and reason for a KP once the PC is totally frozen. 

 

Anyway, you can also just ignore my advice. Fine with me. 

  • Sad 1
kgp
kgp
Posted
Posted (edited)
1 hour ago, arsradu said:

 

Hmm...where did you get this driver? :D

 

Have you tried building with UDK2018? I see you're still using edk2.

Also, no issues booting Mojave using Clover 4538. So...I'm guessing it might be something specific either to your config...or to your Clover build. It's just an idea. I could be wrong. But...as I said, doesn't happen to me.

If you want, you can give it a try.

Clover_v2.4k_r4538.pkg

 

I did not say that I had problems in booting Mojave with 4538. I did say that I witnessed a KP and another error while building 4538 on X299 under Mojave. 

 

I guess one should be able to use the Build_Clover.Command, isn’t it? If the latter requires some update to use UDK2018 instead of edk2, I hope somebody can implement it. 

 

All my previous replies about remaining errors have been valid and kindly removed/fixed by @Slice

 

I don't think that now the remaining error is at my side.. 

Edited by KGP-iMacPro
arsradu
arsradu
Posted
Posted (edited)

The only issue I had building Clover in Mojave is the one I posted above. That’s why I thought I would suggest using UDK2018 method.

 

As for build_clover.command, while an awesome script, it uses SF svn. Which...has been really bad for me recently. Very unstable. By the way, even with VPN.

I don’t know by which miracle it worked last night when downloading Clover sources. But otherwise...man, that was garbage. So...if it works fine for you, that’s great. But an unstable connection like that can create issues building anything. Since you can’t be 100% you got all the sources and nothing is corrupted.

Edited by arsradu
Badruzeus
Badruzeus
Posted
Posted (edited)
23 minutes ago, KGP-iMacPro said:

 

I got a KP while building 4538. It was the first and only one since one year. What else you want yo be proven? You should know yourself that it is impossible to provide proof and reason for a KP once the PC is totally frozen. 

 

Anyway, you can also just ignore my advice. Fine with me. 

Well said, you could troubleshoot your self what caused KP with terminal command like this:

Good luck :)

 

Spoiler

cat /private/var/log/system.log | grep "whatever"

 

Screenshot 35.png

Edited by Badruzeus
  • Like 1
kgp
kgp
Posted
Posted (edited)
12 minutes ago, Badruzeus said:

Well said, you could troubleshoot your self what caused KP with terminal command like this:

Good luck :)

 

  Reveal hidden contents

cat /private/var/log/system.log | grep "whatever"

 

Screenshot 35.png

 

Well.. I see no reason for doing that, sorry.. I usually don't face any KP issues on my system... Thanks for your kind advise anyway... 

 

Also my previous post you originally quoted was addressed to @Slice and I guess he knows quite well that I am talking about.. 

 

The main problem is also not the one single KP I observed while compiling 4538 on X299 under Mojave, but another compiling/buiding error/issue in addition to all others I previously reported and which already have been kindly removed/fixed by others.  

 

Cheers,

 

KGP

Edited by KGP-iMacPro
  • Like 1
vector sigma
vector sigma
Posted
Posted
1 hour ago, KGP-iMacPro said:

I got a KP while building 4538. It was the first and only one since one year. What else you want yo be proven? You should know yourself that it is impossible to provide proof and reason for a KP once the PC is totally frozen. 

Please, are you seriously convinced that this is caused by a build system instead of your beta (almost Alpha) system? You should address the right things to the right persons:

  1. Apple (for the instability of the system)
  2. tianocore (as shown in your log)
  3. pyton devel, again
  4. You system, no one else has this problem, including me.

what this has to do with Clover? Then come back, or wait for a stable system since what are you saying is just incredible.

  • Like 3
kgp
kgp
Posted
Posted
13 minutes ago, vector sigma said:

Please, are you seriously convinced that this is caused by a build system instead of your beta (almost Alpha) system? You should address the right things to the right persons:

  1. Apple (for the instability of the system)
  2. tianocore (as shown in your log)
  3. pyton devel, again
  4. You system, no one else has this problem, including me.

what this has to do with Clover? Then come back, or wait for a stable system since what are you saying is just incredible.

 

My system is absolutely stable although beta.. smoke and mirrors for nothing from your side... no idea why I get offended by you in public for reporting one single KP while compiling 4538 on X299 and Mojave.. 

 

Just ignore my related post if you are more happy like this! 

 

What anyway remains is one more issue when building 4538 on X299 with Mojave using the Clover_Build.command, while in case of 10.13.5 everything works as expected. Further note that there are absolute no issues running X299 with 4538 and 10.14. The issue is solely package building related. 

 

I don't understand why everybody has to comment on my latest post which originally was addressed solely to @Slice and to no-one else...   

 Share
Go to topic listing
×
×
  • Create New...