Jump to content

Philip Petev

Philip Petev

Member Since 13 Oct 2006
Offline Last Active Yesterday, 08:46 PM
*****

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

Posted by Philip Petev on 23 May 2017 - 01:08 PM

Yes, I've changed the preferred NASM version to 2.13.01 inside the script since it's the current stable release, but the script will use any version as long as it's 2.12.02 or later. If you want to upgrade your NASM binary, all you have to do is delete the current one at ~/src/opt/local/bin and the script will download and install the new version on the next run.

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

Posted by Philip Petev on 16 May 2017 - 01:50 PM

I'll look into it later this day. I think the whole function can be optimized

#2423669 Clover General discussion

Posted by Philip Petev on 15 May 2017 - 03:20 AM

fixed i am building Clover with clovergrowerpro....it was calling "makepkg No" fixed it so it calls "makepkg" without an arg CloverGrowerPro... :w00t: That thing was decommissioned long time ago.

#2423484 Clover Bug/Issue Report and Patch

Posted by Philip Petev on 14 May 2017 - 04:06 PM

@Slice: another proposition, courtesy of @Micky1979 1. Clover/CloverPackage/Makefile - three new targets are added for generation of package with removed options: make slimpkg1 - generates install package with removed the Themes subgroupmake slimpkg2 - generates install package with removed the Themes subgroup, Clover Updater and Clover Prefpanemake slimpkg3 - generates install package with removed the Themes subgroup, Clover Updater, Clover Prefpane, the RC scripts and Clover EFI (UEFI boot minimum package only) the make pkg target works as usual 2. The following files are updated to reflect those changes: Clover/CloverPackage/makepkgClover/CloverPackage/package/buildpkg.sh Attached Files  Clover_noextras.zip 13.78KB 3 downloads

#2423367 Clover General discussion

Posted by Philip Petev on 14 May 2017 - 01:45 PM

The Build_Clover.command script has nothing to do with the compiler flags/settings (except choosing the build toolkit: GCCxx or XCODE5/8). Besides, Build_Clover.command only passes options, that are already present in ebuild.sh, based on the user input (selection).

#2423277 Clover Bug/Issue Report and Patch

Posted by Philip Petev on 14 May 2017 - 10:00 AM

@Slice: this is not bug report or patch, more like an improvement. Tested a new code in Build_Clover.command that determines the NASM version, using string-based pattern matching and since that code is the same as the one that does the same in ebuild.sh, made some modifications in it too. The result is code, reduced to only 9 lines, that does the same thing, and all IFS-related stuff, removed from the script. Attached Files  ebuild.sh_noIFS.zip 9.32KB 4 downloads

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

Posted by Philip Petev on 14 May 2017 - 09:44 AM

That package, like every macOS package, can be disassembled, edited and then assembled again, using the pkgutil command line tool (this is the right and proper way). In order to exclude some options, those should be removed from the Distribution script and then the package can be assembled. In any case, the user should know exactly what he's doing. My personal opinion, all that excluding-options stuff is pointless, when there is a choice which component to install or not, especially when nothing will be gain in term of package size (those two are pretty small and the package compression makes them even smaller).

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

Posted by Philip Petev on 13 May 2017 - 04:06 PM

I wouldn't try such things, if I were you, you'll just damage the package. If you don't need those two, use the advanced choice selection and don't install them.  QQ20170513-191828.png 87.19KB 3 downloads QQ20170513-191858.png 128.24KB 3 downloads As you can see, the theme manager is not being installed by default, so just uncheck the other one.

#2405898 Clover General discussion

Posted by Philip Petev on 17 April 2017 - 11:27 AM

@Slice: found a minor issue with ebuild.sh. The script will fail to build Clover on the very first run (the Clover and edk2 sources have just been downloaded), if TOOLCHAIN is set to XCODE8. Currently, the script checks if the mtoc binary is properly installed for TOOLCHAIN, set to XCODE32 and XCODE5, but not if it's set to XCODE8, so the script doesn't extract and install the mtoc binary properly in this case. In order to fix it, line 542:XCLANG|XCODE32|XCODE5) checkXcode ;;should become:XCLANG|XCODE*) checkXcode ;;This way the script will handle all present and future XCODE profiles.

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

Posted by Philip Petev on 11 April 2017 - 05:56 PM

hello nah .. i don't use any theme .. only the built in clover  = embedded good lord .. that don't trouble me .. clover theme thanks Ok, found the cause for that: it's that new XCODE8 compiler profile by @Zenith432. There is something with it that breaks the embedded theme. Tried the same revisions (Clover r4056 and edk2 r24341), compiled with GCC (GCC53) and Xcode (XCODE5), and both builds don't seem to have such problem. Until that thing is fixed, you can workaround the problem by adding XCODE5 to line 34 like this:XCODE="XCODE5"to override the Xcode auto-detection part. Don't forget to use the update Clover + force edk2 update (no building) option before you build Clover.

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

Posted by Philip Petev on 08 April 2017 - 05:50 PM

I successfully compiled with 24341 Same here. Clover r4056, edk2 r24341, Xcode 8.2.1, macOS 10.11.6 and XCODE8 profile. So, we can use that in the script, right? Or...

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

Posted by Philip Petev on 07 April 2017 - 08:22 PM

Alright guys, I have a new version for testing. It has the following changes: 1. The script now auto-detects the Xcode version and sets the proper toolchain profile for it:- for Xcode 8 and later - XCODE8- for Xcode, earlier than 8 - XCODE5LTO will be disabled for Xcode 7.2.x and earlier and enabled for Xcode 7.3.x and later, as usual.The two variables, XCODE and GNU (lines 34 and 35) are still present, but should be used only for overriding the auto-detected values (ex. if you want to use the XCODE5 profile with Xcode 8.x or GCC49 instead of the default profile GCC53)Line 36 contains the setting which build tool to be used - Xcode or GCC. Use only XCODE or GNU as values !!! Any value, different from those two, will cause the script to exit with an error message ! For Linux, that setting is being omitted, because GNU is used by default.2. The script now can compile Clover under Linux Mint 18.x (which is basically rebranded Ubuntu 16.04.x) The test version is HERE as usual....

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

Posted by Philip Petev on 31 March 2017 - 06:59 PM

Close... But not there. xdg-open fails, because there is no graphics server to process that call...That's Bash on Ubuntu on Windows. It's basically stripped-down version of Ubuntu (without X), running on top on the very same kernel that powers Windows! Well, I didn't expect it will work almost out of the box, but theoretically there are no reasons it shouldn't, because it's the same Ubuntu 16.04.1 user space. While the compilation speed can't compare with the compilation speed of Xcode, that user space is very useful for cross-platform compilations (ex. building custom router firmware images like OpenWRT or even Android phone ROMs).Note that this particular Ubuntu version comes with the Windows 10 Creators update that will be released on April 11, the version that comes with the current Windows 10 release (the Anniversary update) is 14.04 and that version can't be used due to the old package base

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

Posted by Philip Petev on 31 March 2017 - 06:12 PM

I see a little show-off goes on here. Ok, this is from me: shot1.png 26.54KB 5 downloads shot2.png 27.75KB 5 downloadsA little joker: that's not Ubuntu :P

#2394491 Clover General discussion

Posted by Philip Petev on 29 March 2017 - 05:16 PM

@Zenith432: nice, but those changes break the compilation with Xcode 8.2.1. Just tested it on OS X 10.11.6, it complaints about unknown warning option (-Wno-address-of-packed-member).  Spoiler Running edk2 build for CloverX64 using the command: build  -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE5 -n 9 Build environment: Darwin-15.6.0-x86_64-i386-64bit Build start time: 20:30:00, Mar.29 2017 WORKSPACE   = /Users/philip/src/edk2 ECP_SOURCE = /Users/philip/src/edk2/EdkCompatibilityPkg EDK_SOURCE = /Users/philip/src/edk2/EdkCompatibilityPkg EFI_SOURCE = /Users/philip/src/edk2/EdkCompatibilityPkg EDK_TOOLS_PATH = /Users/philip/src/edk2/BaseTools CONF_PATH   = /Users/philip/src/edk2/Conf Architecture(s)  = X64 Build target = RELEASE Toolchain   = XCODE5 Active Platform   = /Users/philip/src/edk2/Clover/Clover.dsc Flash Image Definition = /Users/philip/src/edk2/...

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