Jump to content

philip_petev

philip_petev

Member Since 13 Oct 2006
Online Last Active 29 minutes ago
*****

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

Posted by philip_petev on 25 March 2017 - 02:48 PM

Insufficient information. Post the full log.

#2389523 Clover General discussion

Posted by philip_petev on 22 March 2017 - 06:22 PM

remove .metadata_never_index (hidden) from the root of your hd if present. Yeah, that will do, but won't be enough. In most cases, removing that file doesn't automatically enable the indexing, so the following command is required as well:sudo mdutil -i on /

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

Posted by philip_petev on 15 March 2017 - 06:33 AM

Version 4.3.4 is up! This update is recommended for Clover 4038+ is synced with EDK2 r24109

#2384009 Clover General discussion

Posted by philip_petev on 14 March 2017 - 01:12 PM

SourceForge is known to have similar problems from time to time. Just a temporary issue.

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

Posted by philip_petev on 14 March 2017 - 06:26 AM

Alright, version 4.3.3 is up!

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

Posted by philip_petev on 12 March 2017 - 05:08 PM

Guys, I've played with the script the last several days and now it has a new notifications about the script updates and the lines, used for the header, are now drawn by a function. All works perfectly for me, but I'd like to see feedback from more users before I push those changes to the main repo.   The test version 4.3.3 is here (right-click on that link and choose Save as).   For the test purpose, change the script version (the SCRIPTVER="v4.3.3" line) accordingly to 4.3.1, 4.3.2 (the current version) and 4.3.3 and see the version notification at the same line.  ha! .. we should switch to git.. :wacko: As long as @Slice uses the SVN repo, we should use it too. Such change would require rewriting the part regarding the EDK2 updates.

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

Posted by philip_petev on 08 March 2017 - 07:59 AM

... and version 4.3.2 is up.

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

Posted by philip_petev on 07 March 2017 - 06:13 PM

Version 4.3.1 was released at the point when the latest Clover commit was r24045, that's why it has 24045, set as the suggested edk2 revision inside it.Now I see something that I can't say is it curious or funny: the latest edk2 revision is indeed 24061 and yet, the latest Clover revision is synced with edk2 24063. @Zenith432 must have crystal ball or something like that at home !Anyway, until that misunderstanding has been cleared, the suggested Clover revision should stay 24045, who knows, that could be just a typo, but @Zenith432 should clear that mystery.

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

Posted by philip_petev on 07 March 2017 - 05:02 PM

Look at my previous post and the two posts before it.

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

Posted by philip_petev on 07 March 2017 - 04:27 AM

@Badruzeus, there is no issue with the EDK2 version, that version is set to 24045 for a reason: it's the latest EDK2 version that the Clover source is synced with (check the Clover history log). Using any different value than that (especially higher) and the possible consequence is at your responsibility!

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

Posted by philip_petev on 06 March 2017 - 11:56 PM

Done! 4.3.1 is up!

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

Posted by philip_petev on 03 March 2017 - 06:00 PM

I almost forgot about that...Ok, guys, I have rewritten the PrintCloverVer function (it's now printRevisions) and the script shows on startup the local and remote Clover versions or the local and remote Edk2 versions or both, depending of the input parameter, passed to printRevisions. In addition, another message shows is the current local Edk2 version the suggested one or not. You can download the test version 4.3.1 here (right-click on that link and choose Save as).

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

Posted by philip_petev on 03 March 2017 - 07:21 AM

I'll look into this maybe tomorrow. I have an idea about the whole PrintCloverVer function...

#2376413 Clover General discussion

Posted by philip_petev on 02 March 2017 - 01:06 PM

Unless there are some manual operations that require calling the mtoc binary directly by using its name, there's no practical point of symlinking that binary to /usr/local/bin. Wherever that binary could be, its path can be specified and used as a script variable and that binary has no practical usage for most users (besides those who compile Clover) . Just my opinion, the question is for Slice to answer to.

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

Posted by philip_petev on 02 March 2017 - 05:51 AM

@DTK: update your script, then use the update Clover + force edk2 update (no building) option to update your EDK2 source base.

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy