Thanks for the revised script, however I did then see the following:

So I ran sudo xcode-select -switch /Applications/Xcode.app and voila! all fine now.
Well done jadran

This post has been edited by blackosx: Mar 22 2012, 04:04 PM

Glad it works.
Looks like a problem of Xcode 4.3.1
http://developer.appcelerator.com/question...e-path-problems

One another trick:
- install MacPorts (http://www.macports.org/)
- sudo port install apple-gcc42
- use this gcc instead of llmv-gcc

Re-naming my CloverBrewer script to CloverGrower.
While 'brew' is great, its just not up to this task.
Maybe what is needed is a Clover.rb ( brew formula for Clover) Hmmm, another day perhaps.

Using buildgcc.sh instead of 'brew' and 4.7.0 gcc.

Anybody wanting to Grow some Clover, I will post as soon as i debug on my NOT SO CLEAN System.
Can't be bothered installing new system.

@slice, looking good so far, well when I can build again that is.

edit:
This is shaping up really well, stay tuned...

This post has been edited by STLVNUB: Mar 24 2012, 09:06 PM

Can anybody creates a script for creating Installer with customize: 32 or 64, Volume, FAT32 or HFS+, theme?

I am sorry to say this but I have to:

This is going to be as on Linux world, where people spend several time trying to figure out how to build x or y or z, instead spending that precious time to actually develop something.
I don't get the need of building UEFI stuff on OS X, nobody does it and that includes Apple, why we should do so?
The source cannot be builded on Windows so this IMHO is a lost since most of UEFI tools are designed for Windows only, unless Clover will be/work only as a replacement and not designed to work on UEFI boards, and if is like that I don't see the need to replace Chameleon with it.

Sad to see that most developers ignore the very basic UEFI concept, modular, and that includes AMI as others...

Try to build a dual boot Win7-64/OSX on a UEFI board with 3TB disks and you'll see that Chameleon will not work... A UEFI boot loader like Clover will become more important as manufacturers phase out the older BIOS, MBR and MS-DOS partition tables, 32-bit, etc. I do agree that the current state of UEFI implementation and development is a mess...
I think the work Slice is doing is ground-breaking and will become more important over time.

I don't have that much p0rn... j/k


Agree, well the problem is that at this moment Clover is designed as a 'replacement' for the UEFI BIOS(DUET) and does not work in standalone mode(rEFIt)


On Vendors part(read AMI) yes, cant say the same about Insyde or Pheonix(b/c is hard to find something made by them), problem is that any recent board or notebook use ALL AMI APTIO CRAP
EDKII development works good IMHO.


Agree, but, IMHO not as is done now, a mixture of sources(and type of) from various projects, no coding standards(chaos), built on unsupported platform(OS X) with various "tips and tricks" on how to make it, that make people(at least me) to run, and so on...
From the very same reason I didn't got involved too much on Chameleon.

I didn't write previous post or this one to upset or offend someone, far from that, but a signal that things are going in a wrong way in OSX86, in general, and this one, in particular, and may be the reason why not many get involved...

I think the bigger problem we'll face with OSX is that Apple appears to be moving it toward IOS and that means one day they'll likely dump OSX in favor of IOS.

I haven't had the time yet to dive into the source/SDK's to see what Slice has been fighting through, but it sounds like he's been fighting lots of issues in the SDK code. I do plan to test out his solution soon and hope to provide some feedback...

BTW, my laptop also has an Insyde EFI bios that looks and pretends to be an old-school bios... Really bad implementation. At least in this case, Chameleon still works

Have a "new" script CloverGrower.Newest Version ALWAYS ON TOP
Please try it out.
enjoy

Build Clover from ZERO, Well, almost.
You will need Xcode command-line tools already installed.
************************************************************
Newest Versions always in here.

IMPORTANT: Always run CloverGrower.command First, especially when upgrading.

Will always use latest version of GCC, currently 4.7.2

Version 4.9 posted soon


All previous versions withdrawn.

Bugfixes: a few and then some.

Enhancements:V4.8
Someone requested the ability to compile just 64Bit, so type "clover 64" at terminal and it will only compile/build 64bit, BUT no Package at this time.
Package making requires 32/64Bit compilation.

You can place your OWN rc.local and rc.shutdowm.local in User/etc and they will be incorporated into the Package that gets built.
What is rc.local? Good question

rc.local: Run at boot, Used primarily to save Clover ( bios booted ) OR UEFI ( UEFI booted ) boot.log, could easily be used for anything.
rc..shutdown.local: Run at shutdown, Used primarily to save nvram.plist, could easily be used for anything.

***************************************************
Now installs Clover Compile tools to either:
1.
CloverGrowerV3.*/src/CloverTools
2.
/opt/local
3.
/usr/local.
Use Option 1: Keeps it all in the one folder.Compile Tools, Clover source and edk2 source
Use Option 2 or 3, IF you update CloverGrower regularly, You WON'T need to rebuild Compile Tools.

What is it:
CloverGrower is a helper script to download and compile Clover, the NEW UEFI bootloader from Slice.
It does this by utilising available scripts, some tweaked, to download and compile all the tools and
source code necessary to produce a working version of Clover.

How to run:
Extract archive, double click CloverGrower.command

When first run:
1.
Creates link to CloverGrower.command in /usr/local/bin/clover
Then, only need to open terminal and type 'clover' to run CloverGrower.command
run clover h To display help file
2.
Checks for XCode command line tools (gcc) and opens XCode Developer Page IF it is NOT installed, then exits.
You will need top get XCode command line tools and install them, then re-run clover.
3.
Downloads, compiles and installs:
GCC4.7.2 plus the needed tools.
4.
Does a svn checkout of edk2
Builds edk2 BaaseTools
Does a svn checkout of Clover
5.
Copies and re-configures some files in edk2 and Clover using some files in the Files folder.
Then
1) Compiles X64/IA32 Clover/rEFIt
2) Makes pkg
3) archives pkg to BuiltPKG/Clover_revision i.e BuiltPKG/911
4) Opens BuilTPKG

BuiltPKG contains
e.g
CloverCD
Clover_v2_rL911.pkg
Clover_v2_rL911.zip
CloverISO
Clover_v2_rL911.pkg.md5
i386

************************************************************

This post has been edited by STLVNUB: Dec 4 2012, 05:46 AM

Thank you for your hard work. I made a link from first post to your post.
Please provide some explanations and instructions for noobs... Hmm, noobs are going to compile Clover?

Hey Slice, one thing.
How do you do your versions. Like in CloverX64 'info' Clover revision 320 : rEfiT revision 345
My script only produces one, would like to go with your way.
Thanks

All my codes in svn.
I take revision separately in both scripts;
Clover build with cbuld.sh


and refit build with build64.sh

So these Version.h files located in different folders.
And I compile Clover not everytime when I compile refit while version.h are changed with every compilation.

Ok, knew that already. Trying something different in script to fix it here.

Just a suggestion, but why not include EFI folder in svn?
Would certainly make it a bit easier to manage/maintain/build/deploy.

edit:
The problem I have here is if I cd into edk2/Clover and do svn info the revision is actually rEFIt's
same thing for svnversion.
A month or so ago there were 2 revisions, i.e 320:345, now there is one 345.
Seems to be something wrong, but not major problem.

Also, memory info still not displaying correctly in System Information.
First screen "About this Mac" is ok but click on "More Info..." and memory says 4G ????
and error reporting in System Information memory.

This post has been edited by STLVNUB: Mar 31 2012, 05:39 PM

There is still no final decision what is the folder structure should be. But there is a problem to rename or move folders on svn. Delete and then create new.
So this time I will not do this.

This is real values. They depends on how I commit changes. If I commit as a whole Clover folder< then the revision will be the same.
If I commit only rFEIt then revisions will be different.

I don't know why because in Lion sources of AppleSMBIOS became closed. I have only Snow version.

That explains it.
Is it possible to include a txt file like revision.txt in both Clover and rEFIt folders.
I would like to be able to show both firmware values in 'info' and having two separate revision files would make it
easier to do.
Thanks

As a side note:
debugging script on Mnt Lion, found a pkg at
http://cloud.github.com/downloads/kennethr...GCC-10.7-v2.pkg
to give me gcc 4.2
running the script, downloaded 4.6.3 and compiled ok.
No svn found...
Now I need to find svn binaries and script should be almost done...

Then it will be from 'ZERO'...

edit: fixed see
http://www.projectosx.com/forum/index.php?...ost&p=17480

This post has been edited by STLVNUB: Apr 2 2012, 04:20 AM

Hi guys. Can anybody speed me up in understanding flattened dev tree?
Particularly this one here:
 DevTree.png ( 27.77K ) Number of downloads: 47

What is the name here, what is the value, and what could be those two addresses?

Thanks.

Edit: never mind. Found on Google and in sources.

This post has been edited by dmazar: Apr 6 2012, 12:06 PM

And the six million dollar question is:
Where the f**k did the other thread go???

For some reason was set to invisible, guess someone didn't looked on/what buttons, more coffee?
Anyway is set back.

Ok thanks, Phew!!!, thought apple strikes again.