OS X

Oh Snap!

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.

He Loves You Too Deux

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.

He Loves You Too

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.

He Loves You

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 it so

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.

Might I have a quick look?

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.

It's 2:16 a.m. Do you know where your package is?

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.

The Mask!

I remember when I was in college, around either amaroK 1.2 or 1.3 release time, when I first found out about (and was invited to) the amarok dev channel. I don't remember exactlty why, but muesli let me in on the secret. Maybe it was because I was helping out with the docs, or maybe he just wanted to talk about music without the constant distraction of user questions interrupting us :-) Ah yes, good times back then. He turned me on to the awesomeness of Daft Punk and Ol' Dirty Bastard's "Baby I Got Your Money" if I recall correctly.

Things I learned about Xcode today...

There are two ways to include files in your project that guarantees compilation. Only one of these ways should be used at a time.
The first method is the one I learned many moons ago: manually. This uses an #inlcude directive and the path to the file enclosed in quotation marks, i.e. #include "someplace/somefile". The second, Xcode specific method, is checking the "Target" checkbox. This checkbox is in the "Target" column, identifiable by the tiny "target" icon in the column header.
Just in case I lost you.

Recipe for World Domination

After having a talk with aseigo today I have been lulled out of my ill-deserved slumber. So let's try something and see where this goes...

Plan -
Step 1:
Collate an actual list of all KDE's dependencies (Techbase).
Step 2:
Find out which are actually used for functionality on OS X (libagg, opengl).
Step 3. Remove or otherwise move out of the way X11 includes and libraries.
Step 4: Compile and package software only requirements software provided by the base the operating system. Qt first.
Step 5: Repeat Step 4 for the kdesupport software from a stable snapshot.

Syndicate content