Jump to content

Build_Clover.command, another Script to build standard Clover (or customized)

Micky1979

By Micky1979,
in Clover

 Share
2,126 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted

hi Micky

Well, I have restarted the script and always the same

I just look in the script and here's the line that I found

    else
        doSomething --run-script "${PATCHES}/Linux/distribution" # under study (.deb)
    fi

The same that appears in the terminal (See the photo/Spoiler before)

the folder and the script does not exist

Idem here. I do not understand why.

 

No Folders PATCHES="$HOME/CloverPatches" and subfolder /Linux/distribution

  • Like 1
Link to comment
Share on other sites
Philip Petev
Philip Petev
Posted
Posted

I have a proposition about the edk2 update: since a static (specific) version (defined inside the script) is being used, the script should check the version, available online, and should update the edk2 source only if the local version is different or there is no ~/src/edk2 folder.

Link to comment
Share on other sites
Micky1979
Micky1979
Posted
  • Author
Posted

I'm still getting that broken Clover menu with the embedded theme. Script 4.0.7 and Clover 3770.

No idea, I'm not looking into this. maybe Needy or Slice are working on it...

Idem here. I do not understand why.

 

No Folders PATCHES="$HOME/CloverPatches" and subfolder /Linux/distribution

Sorry but what is not clear from posts #432, #433, #434 and #435? You don't want that I'm developing an app to install Clover from Linux and that is not ready? <_<:hysterical:

I have a proposition about the edk2 update: since a static (specific) version (defined inside the script) is being used, the script should check the version, available online, and should update the edk2 source only if the local version is different or there is no ~/src/edk2 folder.

 

Sorry No, you have to use edk2 revision that is compatible with ~/src/edk2/Clover/Patches_for_EDK2/, that does not mean is the lastest available. Otherwise bugs.

I asked Slice to add a txt file with the revision he use to compile Clover more than once... (but also I promis to never ask again :P ). Why is "static"  ^_^

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

 

Sorry but what is not clear from posts #432, #433, #434 and #435? You don't want that I'm developing an app to install Clover from Linux and that is not ready? <_<:hysterical:

 

Sorry for my poor english! I am very slow to write in English. Also I have not seen them before publishing.  :)  :)  :angel_not:  :angel_not:

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

:lol:

Will be an app-installer, so "distribution" is my script that add dependencies where needed an call a GnuMakefile that build the app. 

...that require a lot of time to be finished..

 

Good luck, Bro  :P

  • Like 1
Link to comment
Share on other sites
Philip Petev
Philip Petev
Posted
Posted

 

Sorry No, you have to use edk2 revision that is compatible with ~/src/edk2/Clover/Patches_for_EDK2/, that does not mean is the lastest available. Otherwise bugs.

I asked Slice to add a txt file with the revision he use to compile Clover more than once... (but also I promis to never ask again :P ). Why is "static"  ^_^

 

 

Not my point. Or I wasn't clear enough.

My idea was the script to check what's the current local version of edk2 and to force edk2 update only if the recommended version (set inside the script) has been changes to any higher one or there is no ~/src/edk2 folder at all. It will be a simple check. Currently, the script is trying to pull the recommended edk2 version from the repo on every Clover source update, which IMO is a waste of time.

And yeah, it's static, because it's specific edk2 version, defined by the script (will change significantly rarely than the Clover source).

Link to comment
Share on other sites
Micky1979
Micky1979
Posted
  • Author
Posted

aaah! :D got it.

to do that we should ensure that all these sub dirs have the same revision:

edk2array=(
                BaseTools
                MdePkg
                DuetPkg
                EdkCompatibilityPkg
                IntelFrameworkModulePkg
                IntelFrameworkPkg
                MdeModulePkg
                OvmfPkg
                PcAtChipsetPkg
                ShellPkg
                UefiCpuPkg
            )
+ edksetup.sh 

but can be done.

Link to comment
Share on other sites
Micky1979
Micky1979
Posted
  • Author
Posted

The array comes from what (or was) in /Clover/update.sh:

#!/bin/bash

# the script to update only needed folders from edk2
# to not keep unnecessary Arm*, Beagle, NT32, Unix...

cd ../MdePkg/
svn up
cd ../MdeModulePkg/
svn up
cd ../CryptoPkg/
svn up
cd ../DuetPkg/
svn up
cd ../EdkCompatibilityPkg/
svn up
cd ../IntelFrameworkModulePkg/
svn up
cd ../IntelFrameworkPkg/
svn up
cd ../OvmfPkg/
svn up
cd ../OptionRomPkg/
svn up
cd ../PcAtChipsetPkg/
svn up
cd ../ShellPkg/
svn up
cd ../UefiCpuPkg/
svn up
cd ../BaseTools/Conf
svn up
cd ../Source/
svn up
cd ../Scripts/
svn up
cd ../../Clover/
svn up

so thanks for this because something is changed. But FatPkg is not present and if you look Slice apparently only update BaseTools/Conf and not the entire BaseTools... why?

 

I can read all this into an array doing that (please try):

curl -L https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/update.sh?format=raw | grep 'cd ..' | sed -e 's/^cd ..\///' | sed -e 's/\/$//' | sed -e '/Clover/d'

but what to do with "cd ../BaseTools/Conf"??

 

EDIT

 

also edk2/Source seem to be not present in latest revision...

 

BTW OvmfPkg compile well w/o them 

EDIT II

ok CryptoPkg used for secure boot, but FatPkg is used for ...not already included?.. how can works otherwise?

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

 but FatPkg is used for ...not already included?.. how can works otherwise?

    # Binary INF file to support toggle among different CPU architectures.
#INF  RuleOverride=BINARY FatBinPkg/EnhancedFatDxe/Fat.inf
INF  Clover/FatPkg/EnhancedFatDxe/Fat.inf

 

 

Slice apparently only update BaseTools/Conf and not the entire BaseTools... why?

Yes, my way is not for all. Once I made BaseTools then no more change them until new big event.

  • Like 1
Link to comment
Share on other sites
Micky1979
Micky1979
Posted
  • Author
Posted 
MdePkg
MdeModulePkg
CryptoPkg
DuetPkg
EdkCompatibilityPkg
IntelFrameworkModulePkg
IntelFrameworkPkg
OvmfPkg
OptionRomPkg
PcAtChipsetPkg
ShellPkg
UefiCpuPkg
BaseTools
Source
Scripts

Ok thanks. Looks fine to you to download only the above package at the specified revision than? 

To me seem ok since the fat driver is already included in Clover..

Link to comment
Share on other sites
Slice
Slice
Posted
Posted 
MdePkg
MdeModulePkg
CryptoPkg
DuetPkg
EdkCompatibilityPkg
IntelFrameworkModulePkg
IntelFrameworkPkg
OvmfPkg
OptionRomPkg
PcAtChipsetPkg
ShellPkg
UefiCpuPkg
BaseTools
Source
Scripts

Ok thanks. Looks fine to you to download only the above package at the specified revision than? 

To me seem ok since the fat driver is already included in Clover..

 

Yes, fine.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...