C++

Taming the Leopard

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.

Camping Out

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.

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.

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.

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.

Shpeeeeeeeeeeeeeeeed

I aluded to the speed with which my new macbook can compile softwarez. With the old (1st gen) Macbook Pro I have it takes ~3 hours to compile qt-copy. With this one, ~1 hour. Awesomeness. Here're some hard times for kde module build.

Machine: 2.4 GHz Intel Core 2 Duo Macbook

Time taken to compile:
	kdelibs - real    14m28.700s
	kdepimlibs - real  3m
	kdebase - real    9m18.283s

Touch and no go

I bought a new macbook this weekend because: a) I wanted one, b) I didn't want to wait for Apple's notebook reload and, c) I've become increasingly frustrated by the long compilation times with my (2 year) old Macbook Pro. The good news is its faster, the bad: I don't like it.

Dbus, apartments and phonon

So I'm being a good little boy today and finishing up the coverimagizer nhnfreespirit started helping me with. Looks like I'll need to be reading a little more of my C++ books too. Today's topic: virtual functions. Today's question: Why can't they have explicitly declared destructors? I have to say, looking at other people code makes this coding thing far easier than it would be otherwise. It's also more fun than looking for apartments in Dayton. Moving sucks. Hope I can find someplace close to work though, but I'll worry about that some other day.

Eureka! The computer's got it!

Today after my amarok bundle crashed (yet again), and I got the DrKonqui dialog which began using up 171% of my cpu making my fans go crazy, I remembered something. It was not always so. I remembered that I used to have to wait for the Apple Crash Reporter (ACR) to generate a backtrace (bt) before I could launch Amarok again. The ACR immediately generates a bt when OS X programs crash. This seems to take longer than DrKonqui because, with DrKonqui you could just quit and not generate a bt, which I would frequently do.

Syndicate content