- February, 2008 (5)
- March, 2008 (1)
- April, 2008 (7)
- May, 2008 (8)
- June, 2008 (13)
- July, 2008 (10)
- August, 2008 (6)
- September, 2008 (4)
- November, 2008 (15)
May, 2008
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. |
|||
Two hundred and seventeen point one megabytes. This is the current size of an amarok.app bundle which I have laying in my ~/Applications directory. Problem? First of all, it's about one hundred and seventeen point two megabytes too large for my liking. Secondly, it doesn't work. Point number two is the most vexing but I'll touch on point number one first. "Hey illogic-al," you may ask, "why 99.9 MB?" I'll tell you why. |
|||
When I started out trying to install Amarok on OS X it looked something like this: |
|||
The iPhone beta 5 SDK saved me. I finally have a (relatively) trouble-free version of gcc 4.2 with apple patches. Initially I did have some problems with it. It only started working seemlessly after I completely uninstalled Xcode 3.0, rebooted, then installed Xcode 3.1 from the iPhone SDK. Theoretically the two can be installed alongside each other with the iPhone SDK's command line tools being installed over the older version. All I have left to do now is figure out what libraries and other supporting data amarok needs to run so that I can create a .app bundle. |
|||
I just had another dream again today. I remember it too. I woke up and it was nighttime. There was this foreboding feeling. I started walking, then running - i think. Next thing I know I'm running through a crowd of people. I get to where I'm going, or maybe I don't and then I look up into the sky. I notice that where the moon should be, there is something else instead. It looks like a cell, translucently covering the moon. I realize that despite all this it's bright out, as if the sun were shining. |
|||
This is but a continuation of the story began in Trial and error and followed up in SNAFU. After hitting some snags in compiling KDE source with my homebrew apple-gcc42 from macports; I stumbled, by way of the internets, unto a much easier way to get a version of apple's gcc 4.2 installed: the iPhone SDK. It's @ beta5 so far, seemingly not ready for widespread unleashing to the world. I suspect that's largely due to the iPhone SDK part of the package than it is for the compiler portion. |
|||
Came back from church today and the world took a dump at my door. This shouldn't be surprising to me at all. It's just like the devil to throw adversity your way when your ready to do what God tells you. Knowing the old tricks I'm just going to ignore it and let God "take all my troubles and cares". He wants 'em, he can have 'em. |
|||
I've gotten apple-gcc42 to install AND compile c++ code. This has been a "long, hard battle," but i think I've finally won. I was "inspired" to take up this challenge after lfranchi, one of the amarok developers, pointed out that one of the build errors we were getting (in amarok 2 for OSX) was due to use of an old compiler. We have gcc 4.0.1 with custom apple patches on OS X. We can install updated versions of gcc, but these are vanilla versions of GNU's venerable compiler suite. |
|||