Jump to content
30960 posts in this topic

Recommended Posts

3806?

I tested r3805

 

나의 LG-F410S 의 Tapatalk에서 보냄

i find this message

"build.py...

 : error F002: Failed to build module

/Users/Supreme/src/edk2/Clover/AppleImageCodec/AppleImageCodec.inf [iA32, XCODE5, RELEASE]" when building clover.

3806?

R3806 still not working "cancel hibernate wake"

 

나의 LG-F410S 의 Tapatalk에서 보냄

Updating Clover? Since r3781 (I think) every time I update Clover the installer deletes existing themes, changes config.plist/GUI/Themes to "embedded"  so i have reinstall the theme and edit config, surely this can't be intentional. I decided I might have a problem in the src folder so deleted it and rebuilt it with Mickey's 4.05 script, same result... So for a test I did a clean install on another box and installed r3790. Updated to r3800 and had the same results, surely updates don't require reinstalling the theme and a config.plist edit, I must be missing something... All comments welcome, thanks.

This part of the postinstall script (Post.pkg) should be the cause (or your themes directory):

# Check if theme is found
theme_found=0
themes_installed=()

# Store installed themes
$plistbuddy -c "Add InstalledThemes array" "$CLOVER_INSTALLER_PLIST_NEW" >/dev/null
index=0
while read -r -u3 theme_plist; do
    theme=${theme_plist%/*}
    theme=${theme##*/}
    $plistbuddy -c "Add InstalledThemes:$index string $theme" "$CLOVER_INSTALLER_PLIST_NEW" >/dev/null
    [[ -n "config_theme" && "$config_theme" == "$theme" ]] && theme_found=1
    themes_installed+=("$theme")
    index=$((index + 1))
done 3< <(find "${EFI_ROOT_DIR}"/EFI/CLOVER/themes -iname 'theme.plist' 2>/dev/null)

# Replace theme if theme directory not found
if [[ "$theme_found" -eq 0 ]]; then
    [[ -n "$config_theme" ]] && echo "Theme '$config_theme' (defined in config.plist) not found !" >> "${install_log}"
    default_theme=${themes_installed[0]}
    if [[ -n "$default_theme" ]]; then
        echo "Using default theme '$default_theme'" >> "${install_log}"
        $plistbuddy -c "Delete :GUI:Theme" "$config_plist_file" &>/dev/null
        $plistbuddy -c "Add :GUI:Theme string $default_theme" "$config_plist_file" 2>&1 >> "${install_log}"
    fi
fi

Can you post your themes directory on the ESP to test with it?

Hi guys,

 

Was wondering if anyone knows the proper way to reset nvram? Does it have to be done in a shell or will terminal suffice?

 

Thanks

 

Never mind: Deleting Emuvariable64 solved my problem!

 

If anyone has issues with nvram variables not saved and repeated error message popups at login 1> Test you have a working nvram, 2> If not delete Emuvariable64.efi from Clover 3> retest step 1 and thats it!

Just tried to build latest Clover with CloverGrowerPro.

Had a couple of issues with setting up (not finding isl-0.12.2 ...Failed to connect to gcc.gnu.org port 21: Operation timed out) but found a mirrored site and manually downloaded).

 

After that first build went OK and I installed r3806 via pkg installer and system booted like before. All OK.

 

Then, I used "touch" on one of the .C files and ran Cloverpro again and it came back with:

..
..
..
bla bla bla.
..
..
Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = GCC49

Active Platform          = /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Clover/Clover.fdf

Processing meta-data .... done!
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
make: *** No rule to make target `tbuild'.  Stop.
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseMemoryLib/BaseMemoryLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseLib/BaseLib]


build.py...
 : error F002: Failed to build module
	/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64, GCC49, RELEASE]

- Failed -
Build end time: 01:13:03, Oct.14 2016
Build total time: 00:00:08

Cloverx64  ERROR!!


Ejecting RAM disk
"disk2" unmounted.
"disk2" ejected.
SR-Mac-530:CloverGrowerPro MacNB$ 

Cannot do any more builds.

What wrong and how to fix ?

(I am running on macOS 10.12)

New attempt

attachicon.gifCLOVERX64.efi.zip

 

 

success

New attempt

attachicon.gifCLOVERX64.efi.zip

 

but i found some difference.

 

when i use "NeverHibernate" option on Boot section in config.plist

 

i dont see crash report apple when enter osx wallpaper. but your new attemp file i see this message.

 

try again now compared to before

 

 

okay

i tested r3577 clover version to compared your new file.

post-980913-0-11561600-1476432580_thumb.jpgpost-980913-0-67850300-1476432582_thumb.jpg

 

it's same. clover finally is back like old gui.

 

new file solveed cancel hibernate wake issue

 

thanks :thumbsup_anim:

  • Like 1

Glad Cancel wake is working again :yes:

Any idea about my issue here ?

 

hello

 

use this to build clover .. that is not a issue .. what u are trying to use the script .. no updates .. so don't work

 

http://www.insanelymac.com/forum/files/file/589-build-clovercommand/

 

good hack

  • Like 2

hello

 

use this to build clover .. that is not a issue .. what u are trying to use the script .. no updates .. so don't work

 

http://www.insanelymac.com/forum/files/file/589-build-clovercommand/

 

good hack

 

Thx Artur for quick reply.

 

hmmm...confused.

So what's the point of CloverGroverPro ?

Is it ONLY for building latest Clover and not for experimenting ?

That is, if I want to change a source file, why can't Cloverpro rebuild ?

 

Will clovercommand let me do what I want ?

hello

 

i idk what u want to do .. is not build clover ? .. u can always get clovergropro script and edit the script to ur needs .. is a script .. and make him to work .. must have the skills to do that ..

 

good hack

  • Like 1

Thx Artur for quick reply.

 

hmmm...confused.

So what's the point of CloverGroverPro ?

Is it ONLY for building latest Clover and not for experimenting ?

That is, if I want to change a source file, why can't Cloverpro rebuild ?

 

Will clovercommand let me do what I want ?

Try, there are a lot of options. But please re-download Clover entirely to avoid problems e don't use sources modified by other scripts (off course if that is the case), please.

hello

 

i idk what u want to do .. is not build clover ? .. u can always get clovergropro script and edit the script to ur needs .. is a script .. and make him to work .. must have the skills to do that ..

 

good hack

 

I want to build clover...but my own version where I want to modify a source file (to try to fix something that's has been bugging me) and then rebuild clover.

Any source code control system (or script) should let you change a source file and rebuild the binaries...how else do devs do it ???.

Just like good old makefile, where you setup a set of dependencies and a rule to do 'something' if those dependencies change.

E.g. Binary A depends on objects x, y & z which depends on corresponding sources 1, 2 & 3. If any x,y, z, 1, 2, or 3 changes, then rebuild A.

 

I expected cloverpro to work the same way.

 

I did a git clone (git clone git://github.com/JrCs/CloverGrowerPro.git), then ran clovergrowerpro.sh -s. It spent 30 minutes building a complete toolchain and built a working Clover pkg (which only took 2 minutes).

I then touched one sourcefile to signify a modification and ran clovergrowerpro.sh -n...expecting it simply rebuild clover. But it does not...instead it breaks.

 

I should not have to modify the script that builds a binary just because I changed a source file.

 

Now do you understand what I trying to do ?

Try, there are a lot of options. But please re-download Clover entirely to avoid problems e don't use sources modified by other scripts (off course if that is the case), please.

 

I'll try it when I get home but clovergrowerpro should allow it.

I have raised an issue at sourceforge but not sure if the dev is scanning for issues.

I want to build clover...but my own version where I want to modify a source file (to try to fix something that's has been bugging me) and then rebuild clover.

Any source code control system (or script) should let you change a source file and rebuild the binaries...how else do devs do it ???.

 

 

Developers do it by using an editor changing then saving file(s) push changes to the source control system if there is one and then your standard ./configure, make clean in the case of changes having been made in existing already compiled source tree, make and lastly make install. Or at least that is the method I have seen used/followed in the couple of decades I have been building/re-building from source code when needed by me.

×
×
  • Create New...