Use x86 Boxes to Compile Mac OS X Binaries
IceFox writes "While working on the KDE on Darwin project I have only had one Mac to do development with. At the same time I have been playing around with distcc for Linux/x86 compiling. Combining the two projects I built a Mac OS X cross-compiler (for Linux/x86) and have created the DistccPPCKnoppix distribution. DistccPPCKnoppix is a 46MB Knoppix distribution based on distccKnoppix; with it you can use your extra x86 computers to build Linux/x86 or Mac OS X/PPC binaries. It might not be as shiny as an Xserve cluster, but it is a heck of a lot cheaper."
I am always up for cheap computing power.
I suppose it's worth noting that someone's distributing such a cross-compiler, but the most newsworthy aspect is that it took somebody this long to get around to doing it.
But check out this excerpt from gcc's man pages:Aww man...all my moderation's going to be undone in this discussion now. Well, to the person who said something funny up there: Good job.
Um, yeah, an Xserve is a piece of hardware, and a C-compiler is a piece of software. apples and oranges.
you could install distcc on your Xserve cluster, nnd it (the software) would still be cheap, and it (the hardware) would also be shiny.
Um, i guess the point is that if you want distributed compiling for MacOSX, heretofore the only option was Xserve cluster, and now linux/x86 cluster is also an option. ok ok....
This is great! I do all my development on my 12" Powerbook G4, since I prefer to code in (and for) Mac OS X. That is all good, but it certainly isn't the fastest thing in the world, and I dread having to compile something large like Tex or Mozilla on it. If I was able to get it to do distributed compiles on the numerous Athlons I've got sitting around, it would be awesome.
Random and weird software I've written.
Mac is about the desktop, why not use cheap bland hardware for backend muling.
And that is how it should be, we should be able to select the type of hardware for the job in hand, the software should run wherever it is required.
And if you thought that was boring you obviously havn't read my Journal ;-)
Now all we need is for it to be compatible with Xcode.
--
"Open source is good." - Steve Jobs
"Open source is evil." - Microsoft
If you compiled on ten computers, you could be using more computers to compile the program than actually could run the program.
Hehe I learned my lesson before. I'll be putting the 46MB iso up later tonight, but if someone wants to host it you can e-mail me or im (aim: icefox2) me and I can get you the file.
-Benjamin Meyer
Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
Everything that helps porting all that wealth over to OS X is welcome! :-)
I think, therefore I am...I think.
I thought Apple's gcc was slightly different than the regular gcc - especially in terms of PPC optimizations. If true, then the code output won't be quite the same, will it?
The correct word is "Boxen" not "Boxes". Don't you know it's ironical to spell easy words wr0ng?
And it's also the slashdot way to point out every teh and misused apostrophe.
My father is a blogger.
This is a cool concept. I would think that most Mac users have at least one fast/cheap PC laying around. I know I've got a few of them. You might as well use them for some extra horsepower.
What would be really cool is an x86 agent for iMovie, iDVD, and Final Cut - where it could offload all of the number frunching of MPEG2 compression or other video conversion to some cheap PC's in the basement. I would love to have my 450MHz G4 Cube as the front end, and my Athlon 64 doing the heavy lifting behind the scenes.
Now when is someone going to post binaries for cross-compiling to Mach-O PPC from Sparc's. I've got a bunch of Sun's here I could be using. Granted, I know I could do this myself. But gcc takes so bloody long to compile