illogic-al.Org

He loves you

OS X

Make kde compile in macports in 10.4

Index: kde4-1.0.tcl
===================================================================
--- kde4-1.0.tcl (revision 47836)
+++ kde4-1.0.tcl (working copy)
@@ -31,31 +31,49 @@
# Use CMake Portgroup
PortGroup cmake 1.0

+# Pull in automoc build dependency. Needed by most/all KDE software.
depends_build-append port:automoc

+# Turn on parallel builds.
use_parallel_build yes

+# Create out of source build which KDE requires (and enforces).
worksrcdir build

Being only one post away from breaking my "most posts in a month record" and somewhat making up for the dearth is posting last month, I present to you "Taming the Tiger!". Er, Leopard that is.

This January, God willing and KDE E.V. paying, I'll be in Jamaica for the 1st (hopefully) annual Camp KDE conference. Camp KDE spun out of the KDE 4.0 release event which took place in Mountain View, Cali at Google's place. Legend has it the organizers of the event realized that there were a lot of people who weren't going to the akademies in Europe because they a) couldn't afford it b) had other engangements at that time. I can relate to both points as I was always either in school whenever they had akademy (scheduled too close to end of semester/exam season) or couldn't afford to go.

Just realized that I can go directly to a folder in the Finder by typing [Command]+[Shift]+G. This makes my file browsing experience complete. Now I can open hidden folders without needing to use open /path/to/hidden/.directory in Terminal.app.
Thanks to the Daring Fireball feed which took me to this little gem.

When last we spoke I left on a rather uncertain note. But will it work... I asked. The immediate answer to that query was No. It will not. Being far too persistent with these things I kept on working until the answer was Yes. I have defeated you, vile beast. Yes, dramatic. I know.

Due to the overwhelmingly positive response towards the Amarok 2 packages for Leopard (10.5-intel) (i.e. no one was complaining about how much they sucked) I decided to take a stab at doing universal builds for Tiger (10.4). What would be good about these packages is that they would work for individuals with both powerpc and intel macs. They would also work for users with 10.4 or 10.5 installed, so being able to create them would be a win, win, win, win situation. Kill 4 birds with one stone if you will.

What do you do after working on something for 16 hours? Take a break. A long break. For 4 hours on Friday and 12 straight hours on Saturday I was working on getting my installer package ready. The installer package in question had precious paylod: a beta version of Amarok 2. I finally got it in a state I was comfortable with and released it into the wild. It took quite a bit of work, far more than expected, to get the installer working to my satisfaction. There were some things which I required it to do, or not do, before I was comfortable with releasing it; things which I list below.

Make what so? OS X packages of course! This weekend (actually Labor Day for all us Yanks) a little rose pricked me and reminded me about those packages I was supposed to be making. The friendly poke gave me the activation energy needed to get over the hurdle and get the job started again. That's a little in-joke for the Chem geeks in attendance.

This is a story all about how my life didn't get twist-turned upside down. And I'd like to take some minutes to sit right here, tell you how I became the king of this Apple macbook air.
Kidding! I just didn't want to use "here" to rhyme with "here". That's so unoriginal (if technically correct). So what am I ranting about today while eating my Ichiban? Read on.

I've shifted gears from pretending to being a programmer to now pretending to being a packager. Today's adventure is to get macports to build qt4 as a universal app with gcc4.2. To do this I had to manually symlink g++ to g++-4.2 instead of the default g++-4.0.
This error kind of helped me along.