Jump to content

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


Micky1979
2,126 posts in this topic

Recommended Posts

Thank you very much for the fixes. Everything compiles fine now on my end with build 4571. But...I've got no ApfsDriverLoader anymore. Also, no AptioMemoryFix and AptioInputFix (and probably others I missed). Is that intended...? Are they excluded from the build or something? Cause I didn't get any errors for them while building.

 

Edited by arsradu
Link to comment
Share on other sites

31 minutes ago, arsradu said:

Thank you very much for the fixes. Everything compiles fine now on my end with build 4571. But...I've got no ApfsDriverLoader anymore. Also, no AptioMemoryFix and AptioInputFix (and probably others I missed). Is that intended...? Are they excluded from the build or something? Cause I didn't get any errors for them while building.

 

Depends on what do you use to build Clover:

1. ebuild.sh won't download and add AptioFixPkg/ApfsSupportPkg to the package, unless any of the new -ext-* parameters is specified.

2. Build_Clover.command doesn't use the -ext-* parameters, because it currently has its own subroutines to download, build and add to the package all the mentioned above and it does that by default.

So, the only case you don't get AptioFixPkg/ApfsSupportPkg inside the package is if you use ebuild.sh directly and forgot to use the -ext-* parameters.

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

8 minutes ago, Philip Petev said:

Depends on what do you use to build Clover:

1. ebuild.sh won't download and add AptioFixPkg/ApfsSupportPkg to the package, unless any of the new -ext-* parameters are specified.

2. Build_Clover.command doesn't use the -ext-* parameters, because it currently has its own subroutines to download, build and add to the package all the mentioned above.

So, the only case you don't get AptioFixPkg/ApfsSupportPkg inside the package is if you use ebuild.sh directly and forgot to use the -ext-* parameters.

 

Understood. Thank you very much, Philip, for the clear, yet detailed response.

 

I guess the first one would be my case here. I was only curious if someone else had this issue. Never thought it would be dependent on the "method" used to build Clover.

So, I guess I should do:

./ebuild.sh -ext-*

instead of

 ./ebuild.sh -fr

?

 

Or should I add both?

 

I always wondered what is the -fr parameter for.

Edited by arsradu
Link to comment
Share on other sites

6 minutes ago, arsradu said:

 

Understood. Thank you very much Philip for the clear, yet detailed result

 

I guess the first one would be my case here. I was only curious if someone else had this issue. Never thought it would be dependent on the "method" used to build Clover.

So, I guess I should do:


./ebuild.sh -ext-*

instead of


 ./ebuild.sh -fr

?

 

Or should I add both?

 

I always wondered what is the -fr parameter for.

 

The --ext-* parameters are:

Quote

--ext-pre - downloads the pre-built drivers and adds them to the package

--ext-co - downloads, builds and adds the above to the package

--ext-build - builds the drivers, using the sources, located at ..src/EXT_PACKAGES (must be downloaded already)

 

Edited by Philip Petev
  • Like 3
Link to comment
Share on other sites

On 6/22/2018 at 12:10 AM, arsradu said:

But my question was about APFS: can you boot without apfs.efi on an APFS based system?

it's ebuild.sh, should be:

case "$EXT_DOWNLOAD" in
        1)
          downloadExtDriver "acidanthera/AptioFixPkg" AptioFix "AptioFix-" "-RELEASE"
          downloadExtDriver "acidanthera/ApfsSupportPkg" ApfsSupport "ApfsSupport-v" "-RELEASE"
        ;;
        0 | 2 | 3)
          copyBin "$APTIO_BUILD_DIR_ARCH"/AptioMemoryFix.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/AptioMemoryFix-64.efi
          copyBin "$APTIO_BUILD_DIR_ARCH"/AptioInputFix.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/AptioInputFix-64.efi
          copyBin "$APFS_BUILD_DIR_ARCH"/ApfsDriverLoader.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/ApfsDriverLoader-64.efi
          copyBin "$APFS_BUILD_DIR_ARCH"/ApfsDriverLoader.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64/ApfsDriverLoader-64.efi ;;
      esac

but then also needs this commit to be pushed:https://sourceforge.net/p/cloverefiboot/code/4562/ which is not, otherwise will tells you that you can't add duplicated choices.

 

EDIT

Lol, Slice add it to /Clover... is in the wrong place

EDIT II

should work now see r4577

Edited by vector sigma
  • Like 3
Link to comment
Share on other sites

18 hours ago, Philip Petev said:

Really strange, mkdir is located in /bin and PATH already contains this folder. Please, check if you have the mkdir binary in /bin.

yes mkdir is present in bin, if I try with Xcode 10 beta 2 installed in application folder the script print this message:

 

Unknown Xcode version format, exiting!

Edited by mick3lson
Link to comment
Share on other sites

46 minutes ago, mick3lson said:

yes mkdir is present in bin, if I try with Xcode 10 beta 2 installed in application folder the script print this message:

 

Unknown Xcode version format, exiting!

 

What Build_Clover.command's version?  the current is v4.8.8

 

Do you launch Xcode 10 Beta once for installing command lines tools?

 

Sorry for my bad english

Link to comment
Share on other sites

6 minutes ago, Matgen84 said:

 

What Build_Clover.command's version?  the current is v4.8.8

 

Do you launch Xcode 10 Beta once for installing command lines tools?

 

Sorry for my bad english

Yes I'm using version 4.8.8 Xcode how to install command line tools.

Link to comment
Share on other sites

3 minutes ago, mick3lson said:

Yes I'm using version 4.8.8 Xcode how to install command line tools.

You have to launch Xcode. At first time, the app install command lines tools.

Edited by Matgen84
Link to comment
Share on other sites

2 minutes ago, mick3lson said:

Yes is installed at first boot now I'm launched GIT command in terminal for install command line developer tool.

Git command is not necessary for install command lines developer tools. Xcode just did it.

Link to comment
Share on other sites

  • xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Unknown Xcode version format, exiting!

 

Anyone can upload 4.8.8 version of Buil_Clover.command

Edited by mick3lson
Link to comment
Share on other sites

  • xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Unknown Xcode version format, exiting!

 

Anyone can upload 4.8.8 version of Buil_Clover.command
Check downloads section. I uploaded one

Sent from my SM-G930F using Tapatalk

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

10 minutes ago, mick3lson said:
  • xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Unknown Xcode version format, exiting!

 

Anyone can upload 4.8.8 version of Buil_Clover.command

If you use git command, maybe there is confusion. Best way: uninstall all Xcode, all command lines tools. Re-install as I say before

 

For build_clover.command see: Build_Clover.command

Edited by Matgen84
Link to comment
Share on other sites

On 6/23/2018 at 5:41 PM, mick3lson said:
  • xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Unknown Xcode version format, exiting!

 

Anyone can upload 4.8.8 version of Buil_Clover.command

You need to select the Xcode version in Xcode Preferences for the Command Line Tools.

Open Xcode go to Preferences select Locations and then from the Command Line Tools select the xCode version accordingly.

1911268199_ScreenShot2018-06-28at8_30_18PM.png.0391fce4580aefa8e67adbb0fe5c0d26.png

 

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

53 minutes ago, Cyberdevs said:

You need to select the Xcode version in Xcode Preferences for the Command Line Tools.

 

Open Xcode go to Preferences select Locations and then from the Command Line Tools select the xCode version accordingly.

Ok thank's now work flawlessy, this was the issue.

Edited by mick3lson
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

Hi

 

For commits r4584----> sync edk2 27429. For the script 4.8.8  remote revision is 27425? Which  is the good version!

Edited by Matgen84
Link to comment
Share on other sites

37 minutes ago, Matgen84 said:

Hi

 

For commits r4584----> sync edk2 27429. For the script 4.8.8  remote revision is 27425? Which  is the good version!

 

Either version is good 27425 or 27429.

I sync from edk2 git, which is ahead of svn by around 16 commits.

So I wrote r27429 which is the future svn version of the git commit I synced to.

However the sync is only spaces and comments because they cleaned up their code.

So you can safely use the patch_for_r27429 with r27425.  In a few days 27429 will show up and all will be ok.

  • Like 2
Link to comment
Share on other sites

1 minute ago, Zenith432 said:

 

Either version is good 27425 or 27429.

I sync from edk2 git, which is ahead of svn by around 16 commits.

So I wrote r27429 which is the future svn version of the git commit I synced to.

However the sync is only spaces and comments because they cleaned up their code.

So you can safely use the patch_for_r27429 with r27425.  In a few days 27429 will show up and all will be ok.

Thanks a lot :)

Link to comment
Share on other sites

4 hours ago, Pavo said:

Anyone have instructions on how to build Clover using UDK2018 instead of EDK2?

Hi

 

You can use cvad's app in this forum Clover third party section. Work well. 

 

Link to comment
Share on other sites

×
×
  • Create New...