Jump to content

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


Micky1979
2,126 posts in this topic

Recommended Posts

@Badruzeus

Can you please share your build_clover.command?

I want to cross reference my script with the one that you use.

5 minutes ago, KGP-iMacPro said:

I face exactly the same issue.. with new Build Clover command no APFSDriverLoader-64.efi.. 

Yeah we are not the only ones that have this issue as far as I know. Several other users have the same issue with the latest version.

  • Like 3
Link to comment
Share on other sites

Hi @Philip Petev

 

To solve problem with ApfsDriverLoader:

  • Is it possible to introduce --ext-co args for ebuild.sh: clover manages additional drivers (aptio, apple support...), create a directory src/ext_package, etc
  • Or convert Build_Clover.command EDK2 script to UDK2018 

Thanks

Edited by Matgen84
Link to comment
Share on other sites

2 hours ago, Cyberdevs said:

@Badruzeus

Can you please share your build_clover.command?

I want to cross reference my script with the one that you use.

Yeah we are not the only ones that have this issue as far as I know. Several other users have the same issue with the latest version.

Sorry, bit late to reply.. But I'm using a same build_clover script v4.9.1 FYI. Just updated a moment ago, r4647 also built succeeded with EDK2 r27429, including ApfsDriverLoader-64.efi (AppleSupportPkg r185). Plz check your ~/src/edk2/Clover/ebuild.sh << if you've manually edited some lines, then maybe there're some unresolved conflicts when gotta update from SF (or simply compare with my attached file below). Here's my Clover v2.4k r4647.pkg. Thanks.

ApfsDriverLoader-64.png

Build_Clover_v4.9.1_ebuild.sh.zip

Build_Clover_v4.9.1_logs.zip

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

13 minutes ago, Badruzeus said:

Sorry, bit late to reply.. But I'm using a same build_clover script v4.9.1 FYI. Just updated a moment ago, r4647 also built succeeded with EDK2 r27429, including ApfsDriverLoader-64.efi (AppleSupportPkg r185). Plz check your ~/src/edk2/Clover/ebuild.sh << if you've manually edited some lines, then it maybe there're some unresolved conflicts when gotta update from SF (or simply compare with my attached file below). Here's my Clover v2.4k r4647.pkg. Thanks.

Thanks for the files man, they are identical with the files I have, I'm not sure why it's not working on my end (or the other members)

I'm using Xcode 9.4.1 on High Sierra 10.13.6

I didn't edit the ebuild.sh and the local EDK2 revision is also 27429 so I wonder what can be the cause!

  • Like 2
Link to comment
Share on other sites

10 minutes ago, Cyberdevs said:

Thanks for the files man, they are identical with the files I have, I'm not sure why it's not working on my end (or the other members)

I'm using Xcode 9.4.1 on High Sierra 10.13.6

I didn't edit the ebuild.sh and the local EDK2 revision is also 27429 so I wonder what can be the cause!

Uhmb, what if you find "ApfsSupportPkg" (I mean, keyword search) from your "~/src/edk2/" dir?

Edited by Badruzeus
Link to comment
Share on other sites

5 minutes ago, Badruzeus said:

Uhmb, what if you find "ApfsSupportPkg" from your "~/src/edk2/" dir?

it's there. I removed the whole edk2 folder and updated the src/edk2 as well, but no luck so far.

How ever when I use Did's script it builds the package with no issue.

Link to comment
Share on other sites

6 minutes ago, Cyberdevs said:

it's there. I removed the whole edk2 folder and updated the src/edk2 as well, but no luck so far.

How ever when I use Did's script it builds the package with no issue.

Using UDK, I've just been warned with "ebuild.sh" changes from SF previously with new ApfsSupportPkg project moved, (not remember exactly) but I clicked Yes, Yes, Accept and it has NP.

 

#EDIT: That was bcoz, I edited ~/udk/UDK2018/Clover/ebuild.sh manually b4 SF update #LoL

Edited by Badruzeus
Link to comment
Share on other sites

HI

always same error with v4.9.1 script on clean src folder: apfsdriverloader failed to build (build.py error 4000....)

 

Any solutions? :cry:

Edited by Matgen84
Link to comment
Share on other sites

HI
always same error with v4.9.1 scrip on clean src folder: apfsdriverloader failed to build (build.py error 4000....)
 
Any solutions? :cry:
me too. even i installed clean mojave yesterday. still happen like you

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 2
Link to comment
Share on other sites

5 minutes ago, Matgen84 said:

HI

always same error with v4.9.1 scrip on clean src folder: apfsdriverloader failed to build (build.py error 4000....)

 

Any solutions? :cry:

Nope nothing so far.

I've been testing on various systems and no luck so far.

The APFSDriverLoader won't be compiled and/or being called from the git into the drivers folder no matter what.

  • Like 2
Link to comment
Share on other sites

It's weird, why using OS X 10.11.6, Xcode 8.2.1 with same nasm version, a same script.. I get no issue at all? Uhmb, I don't think it bcoz GH / SF connection issue. Already tried with svn co / https as well as via VPN, it's still succeeded built. How if replacing AppleSupportPkg dir on EDK2 from UDK2018?

Link to comment
Share on other sites

4 minutes ago, Badruzeus said:

It's weird, why using OS X 10.11.6, Xcode 8.2.1 with same nasm version, a same script.. I get no issue at all? Uhmb, I don't think it bcoz GH / SF connection issue. Already tried with svn co / https as well as via VPN, it's still succeeded built. How if replacing AppleSupportPkg dir on EDK2 from UDK2018?

if I use ./makepkg it will build successfully with the APFSDriverLoader.efi (UDK of course) but no luck with the EDK2 :wacko:

  • Like 1
Link to comment
Share on other sites

2 hours ago, Cyberdevs said:

if I use ./makepkg it will build successfully with the APFSDriverLoader.efi (UDK of course) but no luck with the EDK2 :wacko:

Not sure if this will help, but you may try..

rm -rf ~/Library/Developer/Xcode/DerivedData/*

And what I meant on prev. reply from "~/src/edk2" root is..

Screenshot 27.png

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

Hi

To solve problem with ApfsDriverLoader:

  • How to modify script to add --ext-co args for ebuild.sh: clover manages additional drivers (aptio, apple support...), create a directory src/ext_package, etc
  • or convert to UDK2018 script

Thanks

Link to comment
Share on other sites

14 minutes ago, Badruzeus said:

Not sure if this will help, but you may try..


rm -rf ~/Library/Developer/Xcode/DerivedData/*

And what I meant on prev. reply from "~/src/edk2" root is..

Nope didn't fix it so far I'm downloading the src once more.

 

1 minute ago, Matgen84 said:

Hi

To solve problem with ApfsDriverLoader:

  • How to modify script to add --ext-co args for ebuild.sh: clover manages additional drivers (aptio, apple support...), create a directory src/ext_package, etc
  • or convert to UDK2018 script

Thanks

check this link provided by @Slice

https://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/?do=findComment&amp;comment=2614159

 

or just run this command instead:

https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=305796

  • Like 2
  • Sad 1
Link to comment
Share on other sites

39 minutes ago, Cyberdevs said:

Nope didn't fix it so far I'm downloading the src once more.

 

check this link provided by @Slice

https://www.insanelymac.com/forum/topic/282787-clover-v2-instructions/?do=findComment&amp;comment=2614159

 

or just run this command instead:

https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=305796

 

Thanks a lot :) I know and use Dids script (UDK2018). I did not express myself well: convert buil_clover.command to script UDK2018 instead of EDK2.

 

 

For now by copying only one file from UDK2018 folder to EDK2 folder, I can build apfsdriverloader with v4.9.1: /Users/mathieu/src/UDK2018/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf to /Users/mathieu/src/EDK2/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf

 

EDIT: for BBedit, these two files are identical

 

Capture d’écran 2018-08-16 à 16.23.43.png

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

18 minutes ago, Matgen84 said:

Thanks a lot :) I know and use Dids script (UDK2018). I did not express myself well: convert buil_clover.command to script UDK2018 instead of EDK2.

 

 

For now by copying only one file from UDK2018 folder to EDK2 folder, I can build apfsdriverloader with v4.9.1: /Users/mathieu/src/UDK2018/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf to /Users/mathieu/src/EDK2/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf

Thanks to you that did the trick for ma as well, now the APFSDeriverLoader is included in the build as well.

 

About your initial question honestly I don't know how to convert the existing command to build with UDK2018 instead of EDK2.

  • Thanks 1
Link to comment
Share on other sites

7 minutes ago, Cyberdevs said:

Thanks to you that did the trick for ma as well, now the APFSDeriverLoader is included in the build as well.

 

About your initial question honestly I don't know how to convert the existing command to build with UDK2018 instead of EDK2.

For UDK build I just use bash script kiddie like this #LoL.. for update & makepkg only. Oh, I mv ~/src ~/udk #btw.

Spoiler

#!/bin/bash

cd ~/udk/UDK2018/
svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
cd Clover
./ebuild.sh --ext-co -fr
cd ~/udk/UDK2018/Clover/CloverPackage/
./makepkg

echo -e "Clover Bootloader package has been built successfully!"
exit

 

 

Any idea with Slim package (excluding Themes && CTM.app) using UDK?

  • Like 1
Link to comment
Share on other sites

14 minutes ago, Badruzeus said:

For UDK build I just use bash script kiddie like this #LoL.. for update & makepkg only. Oh, I mv ~/src ~/udk #btw.

  Hide contents


#!/bin/bash

cd ~/udk/UDK2018/
svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
cd Clover
./ebuild.sh --ext-co -fr
cd ~/udk/UDK2018/Clover/CloverPackage/
./makepkg

echo -e "Clover Bootloader package has been built successfully!"
exit

 

 

Any idea with Slim package (excluding Themes && CTM.app) using UDK?

 

Have a look in clover package/makefile. Maybe, it's will help you

#	Makefile for kernel booter
SRCROOT = $(CURDIR)
# Reset default charset for GNUsed problems...
LC_ALL=C
export LC_ALL

image iso: utils
	@${SRCROOT}/makeiso

pkg installer:
	@${SRCROOT}/makepkg

slimpkg1:
	@${SRCROOT}/makepkg --nothemes

slimpkg2:
	@${SRCROOT}/makepkg --nothemes --noprefpane

slimpkg3:
	@${SRCROOT}/makepkg --nothemes --noprefpane --norc --nolegacy

updatepo:
	@${SRCROOT}/package/translate.sh --update-po

utils:
	@make -C "${SRCROOT}"/utils all

install:
	@make -C "${SRCROOT}"/utils install

clean:
	rm -rf sym obj dst CloverPrefpane/build CloverUpdater/build

.PHONY: clean image iso pkg installer updatepo utils

 

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

23 minutes ago, Badruzeus said:

For UDK build I just use bash script kiddie like this #LoL.. for update & makepkg only. Oh, I mv ~/src ~/udk #btw.

  Reveal hidden contents


#!/bin/bash

cd ~/udk/UDK2018/
svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
cd Clover
./ebuild.sh --ext-co -fr
cd ~/udk/UDK2018/Clover/CloverPackage/
./makepkg

echo -e "Clover Bootloader package has been built successfully!"
exit

 

 

Any idea with Slim package (excluding Themes && CTM.app) using UDK?

use these:

cd ~/src/UDK2018/Clover/CloverPackage/

./makepkg --notheme

 

Usage: ./makepkg [flag1 flag2...]

 

The (optional) exclude flags are being passed to the buildpkg.sh script, when specified.

Possible flag values:

 

--nothemes Excludes the Themes subpackage.

--noprefpane Excludes the Clover Prefpane / Clover Updater subpackage.

--norc Excludes the RC scripts subpackage.

--nolegacy Excludes the CloverEFI subpackages.

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

HI

 

same issue, same solution her on Mojave Beta 7: replace DxeServicesLib.inf

Build environment: Darwin-18.0.0-x86_64-i386-64bit
Build start time: 17:56:34, Aug.16 2018

WORKSPACE        = /Users/mathieu/src/edk2
ECP_SOURCE       = /Users/mathieu/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/mathieu/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/mathieu/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/mathieu/src/edk2/BaseTools
CONF_PATH        = /Users/mathieu/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/mathieu/src/edk2/AppleSupportPkg/AppleSupportPkg.dsc

Processing meta-data .

build.py...
/Users/mathieu/src/edk2/AppleSupportPkg/AppleSupportPkg.dsc(...): error 4000: Instance of library class [HobLib] is not found
	in [/Users/mathieu/src/edk2/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf] [X64]
	consumed by module [/Users/mathieu/src/edk2/AppleSupportPkg/Platform/AppleImageLoader/AppleImageLoader.inf]
 

- Failed -
Build end time: 17:56:35, Aug.16 2018

 

Link to comment
Share on other sites

Open src/EDK2/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf

 

Change this line

#  VALID_ARCHITECTURES           = IA32 X64 IPF EBC ARM AARCH64
 

To

  VALID_ARCHITECTURES           = IA32 X64 IPF EBC ARM AARCH64
 

Now we can compile AppleSupportPkg.

  • Like 2
Link to comment
Share on other sites

36 minutes ago, zhangqq said:

Open src/EDK2/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf

 

Change this line

#  VALID_ARCHITECTURES           = IA32 X64 IPF EBC ARM AARCH64
 

To

  VALID_ARCHITECTURES           = IA32 X64 IPF EBC ARM AARCH64
 

Now we can compile AppleSupportPkg.

 

Good idea. What is the difference between these two lines. It seems identical except uncommented line, I think.

Edited by Matgen84
Link to comment
Share on other sites

×
×
  • Create New...