Clover General discussion

[Matgen84]

16 minutes ago, arsradu said:

Hi Pene!

 

Yeah, that's how I always do it when I wanna build on a clean environment. Can't get any cleaner than that! :)))

 

However, it still occurs.

 

Do you use Xcode or GCC! For me, I use Xcode.

 

What speed do you have for cloning repo? Yesterday, I've 235Kb/s and to day more 1,7Mb/s

 

 

Edited March 22, 2020 by Matgen84

[arsradu]

4 minutes ago, Matgen84 said:

 

Do you use Xcode or GCC! For me, I use Xcode.

Uhm... I don't know. Which one is the default one?

 

This is the list of commands I use:

cd ~
mkdir src
cd src
git clone https://github.com/CloverHackyColor/CloverBootloader
cd CloverBootloader
./buildme (select Option 3)

 

[Matgen84]

5 minutes ago, arsradu said:

Uhm... I don't know. Which one is the default one?

 

This is the list of commands I use:

cd ~
mkdir src
cd src
git clone https://github.com/CloverHackyColor/CloverBootloader
cd CloverBootloader
./buildme (select Option 3)

 

 

I believe default is GCC53. But you must select Option 1 at first (scratch src) then option 3. Option 1 install nasm...

 

Test in progress here with GCC53 command (new GCC9.3)

Edited March 22, 2020 by Matgen84

[arsradu]

23 minutes ago, Matgen84 said:

 

I believe default is GCC53. But you must select Option 1 at first (scratch src) then option 3. Option 1 install nasm...

I see. So this is what I was missing. But weird thing is that I don't remember having to do that before... Maybe because I usually used option 6 (build all)?

 

Anyway, it does work fine now, with Option 1 first, then Option 3. Thank you!

 

So which one is that? GCC or Xcode? Or do i need to do that for both? How do I use one or the other?

 

Update: yeah, that's definitely what I was missing. I was using Option 6 before, which took care of everything. Now I tried clean source with only Option 3 which clearly needs some preparation to be done before being used. :))

 

Definitely my mistake. Sorry about that.  

Edited March 22, 2020 by arsradu

[Pene]

1 hour ago, arsradu said:

Hi Pene!

 

Yeah, that's how I always do it when I wanna build on a clean environment. Can't get any cleaner than that! :)))

 

However, it still occurs.

Hi arsradu,

 

Looking at your previously published log, it seems to me that the failure is somewhere earlier, as you have several files that should have been produced in first stage that are missing.

Please post your complete log, as I cannot reproduce the error on my system.

 

EDIT: Ah, yes, I was too late, so it is all clear now, no need to post anything 

But maybe it's not a bad idea to add some checks to buildme for option 3, to ensure some basic files exists.

 

Edited March 22, 2020 by Pene

[Matgen84]

7 minutes ago, arsradu said:

I see. So this is what I was missing. But weird thing is that I don't remember having to do that before... Maybe because I usually used option 6 (build all)?

 

Anyway, it does work fine now, with Option 1 first, then Option 3. Thank you!

 

So which one is that? GCC or Xcode? Or do i need to do that for both? How do I use one or the other?

 

The procedure is the same for Xcode and gcc for a first installation. Then, option 1 is only used for rebuild when there are problems, if I'm not mistaken. I believe that the developer of Clover use GCC, personally I prefer xcode. It's up to you.

Theoretically, option 6 should do it all, rebuild, pkg, iso, app after first build option 1. I don't know  if my reasoning is correct.

[arsradu]

8 minutes ago, Pene said:

Hi arsradu,

 

Looking at your previously published log, it seems to me that the failure is somewhere earlier, as you have several files that should have been produced in first stage that are missing.

Please post your complete log, as I cannot reproduce the error on my system.

 

 

Hi Pene!

 

You're right. They should have.  And they weren't, cause I went directly with Option 3 (make pkg) without using Option 1 first. My mistake. Usually, I was using Option 6 (build all) to build. That's why I didn't see this issue before.

 

No need for a log. It's all good now. I understood where the error came from. My bad.  

 

7 minutes ago, Matgen84 said:

 

The procedure is the same for Xcode and gcc for a first installation. Then, option 1 is only used for rebuild when there are problems, if I'm not mistaken. I believe that the developer of Clover use GCC, personally I prefer xcode. It's up to you.

Theoretically, option 6 should do it all, rebuild, pkg, iso, app after first build option 1. I don't know  if my reasoning is correct.

 

For as far as I can see, if you're using Option 6, you don't need Option 1 anymore. Option 6 includes everything.

Edited March 22, 2020 by arsradu

[Matgen84]

1 hour ago, arsradu said:

For as far as I can see, if you're using Option 6, you don't need Option 1 anymore. Option 6 includes everything.

 

For testing, I only use Option 1, only after cloning clover directory to src. I never use Option 6: for daily build, I use make pkg and make app, that's all.

Right, Option 6 includes everything.  Strange.

[vector sigma]

What is strange? It is strange to do it step by step if you want all the step.

if I'm working on the package, I build only the package.

if I'm working on Clover, I build only Clover.

if I'm working on the app, I build the app

If I want everythings just select 6 

 

P.S. also cloning into the ~src is no longer a requirement, unless you have more then one Clover source here and there (and so share the same opt directory)

6 hours ago, arsradu said:

Which one is the default one?

The default is GCC53 because is better. If some times the same code build with xcode and  not with gcc is because Xcode (clang) is less aggressive finding potential errors. Or at least the settings defined for the GCC toolchain are actually better. ..and the LTO with GCC appear to do a great job, imho.

Edited March 22, 2020 by vector sigma

[Sherlocks]

9 minutes ago, vector sigma said:

What is strange? It is strange to do it step by step if you want all the step.

if I'm working on the package, I build only the package.

if I'm working on Clover, I build only Clover.

if I'm working on the app, I build the app

If I want everythings just select 6 

 

P.S. also cloning into the ~src is no longer a requirement, unless you have more then one Clover source here and there

The default is GCC53 because is better. If some times the same code build with xcode and  not with gcc is because Xcode (clang) is less aggressive finding potential errors. Or at least the settings defined for the GCC toolchain are actually better. ..and the LTO with GCC appear to do a great job, imho.

 

i'm not type sudo when using buildme.

i added this

 

#!/bin/bash

version=1.1
cloverLink='https://github.com/CloverHackyColor/CloverBootloader.git'

ask() {
read -p "$1 [Y/n] " -n 1 -r
if [[ ! $REPLY =~ ^[Yy]$ ]]; then
  echo && echo "sorry can't help!"
  exit 0
fi
}

echo && echo clovergit v$version

if [[ ! -d "$HOME"/src/CloverBootloader ]]; then
  ask 'Do you want to checkout CloverBootloader?'
  mkdir -p "$HOME"/src
  cd "$HOME"/src
  #git clone --depth 1 $cloverLink
  git clone $cloverLink
fi

sudo "$HOME"/src/CloverBootloader/./buildme XCODE8

 

there is no problem.

 

clovergit_v1.1.zip

[Matgen84]

4 minutes ago, vector sigma said:

What is strange? It is strange to do it step by step if you want all the step.

if I'm working on the package, I build only the package.

if I'm working on Clover, I build only Clover.

if I'm working on the app, I build the app

If I want everythings just select 6 

 

P.S. also cloning into the ~src is no longer a requirement, unless you have more then one Clover source here and there

 

Thanks for your great work @vector sigma I don't speak english fluently. I just answers to @arsradu questions on scratch cloverbootloader folder: so read his questions before.

 

[vector sigma]

Just now, Sherlocks said:

sudo "$HOME"/src/CloverBootloader/./buildme XCODE8

Using sudo the worst thing you can do. Please don't do that. Why you do that?

1 minute ago, Matgen84 said:

so read his questions before.

I did it, but I answered to you not to arsradu

[Sherlocks]

3 minutes ago, vector sigma said:

Using sudo the worst thing you can do. Please don't do that. Why you do that?

I did it, but I answered to you not to arsradu

 

really? if there is no sudo, rm permission not work when build pkg. i don't know it exactly.

[arsradu]

7 minutes ago, Sherlocks said:

git clone --depth 1 $cloverLink

Regarding this (cloning with --depth 1) I remember there were some issues, because it would not download everything. So...personally I don't use it anymore.

[Matgen84]

3 minutes ago, vector sigma said:

I did it, but I answered to you not to arsradu

 

Keep cool, bro  I don't speak English fluently (I repeat), so I sometimes use words that are not the right ones. Yes I know the different stages, rest assured.

[vector sigma]

Just now, Sherlocks said:

 

really? if there is no sudo, rm permission not work when build pkg. i don't know it exactly.

So you did something wrong because, unless your source is inside a volume that your account cannot access, no thing inside the source is setting root permissions other than yours.

2 minutes ago, arsradu said:

Regarding this (cloning with --depth 1) I remember there were some issues, because it would not download everything. So...personally I don't use it anymore.

Because having only last commit you don't have tags (used to retrieve the Clover revision). you can use --depth, but you should ensure to include the last tag

[arsradu]

23 minutes ago, vector sigma said:

P.S. also cloning into the ~src is no longer a requirement, unless you have more then one Clover source here and there (and so share the same opt directory)

 

Oh, cool. I didn't know that. I only have one source right now. So yeah, might not be necessary to keep it under /src anymore. I didn't know that. Good to know.

[vector sigma]

3 minutes ago, Matgen84 said:

Keep cool, bro  

Yes , do you think I was mad? 

[arsradu]

3 minutes ago, vector sigma said:

Because having only last commit you don't have tags (used to retrieve the Clover revision). you can use --depth, but you should ensure to include the last tag

 

Oh I see!  I've learned something new today. Thank you!

[Matgen84]

Just now, vector sigma said:

Yes , do you think I was mad? 

 

Not at all   Me I'm mad 

[vector sigma]

Just now, Matgen84 said:

 

Not at all   Me I'm mad 

Why?

[Sherlocks]

Latest Clover is still perfect on old macos.:)

i tested it today on 2020

[arsradu]

3 minutes ago, vector sigma said:

Yes , do you think I was mad? 

 

Yes, mad scientist. LOL

[Matgen84]

3 minutes ago, vector sigma said:

Why?

 

Because Covid-19 restrictions in France where I live  

[vector sigma]

1 minute ago, arsradu said:

 

Yes, mad scientist. LOL

see at my cat