In Which I Solve More of Your Most Pressing Problems

Look at this bullshit. I’ve been trying to get plotting and Qt working under Lisp, on a Mac, because I fucking hate myself. Yinz are about to benefit from my experience.

Here are the steps if you are the kind of self-hating masochist who needs to get commonqt working under OS X:

Steps to do that:

1) use something like macports to get the smoke libraries, e.g.

sudo port install smokeqt

2) wait a long time, hopefully it finishes without exploding

3) if you’ve got quicklisp, do (ql:quickload "qt"). It will crash.

4) It crashes for the following reasons:

a) for reasons not obviously clear to me the compilation is linked against the debug libraries, i.e. libQtGui_debug. WHY?! It don’t matter, go to whatever directory quicklisp put your shit in and edit the commonqt.pro file to remove the debug from the build spec.
b) While you’re there you’ll also want to change lsmokeqtcore to lsmokebase because that’s the correct lib to link against, else CRASHX0R.

5) ok, you can now (ql:quickload "qt") again. Psych! no you can’t. It won’t work. WHY?!

6) it’s because the cffi library that gets loaded is incorrectly configured for OS X. That’s fucking right, you’re gonna want to change that line in info.lisp that goes:

#-(or mswindows windows win32) "libsmoke~A.so"

to something sensible like

#+(and (or unix) (not darwin)) "libsmoke~A.so"
#+(or mswindows windows win32) "smoke~A.dll"
#+(or darwin) "libsmoke~A.dylib"

so that now it actually loads libsmokecore.dylib and all that other jazz correctly.

7) ok, now run the quickload again! YOU ARE ALL SET MOTHERFUCKER.

How to solve the problem of multiple Qt installations on a Mac

Yeah, I know; this is probably not a common problem you have. But shit, this is as much or more for my benefit as yours. Anyway, let’s say you have Qt installed because you downloaded the official dmg, but then you also went and installed the Enthought Python distribution which comes with its own Qt. And also, that Qt might be a different architecture, so WHAT CAN YOU DO?!

Just export DYLD_FRAMEWORK_PATH, like so:

export DYLD_FRAMEWORK_PATH="/Library/Frameworks/Python.framework/Versions/7.2/Frameworks/:$DYLD_FRAMEWORK_PATH"

This should ensure that any loading of the Qt libraries references the Enthought ones. Of course yours might be installed in a different location (and in any case instead of referencing version 7.2 you should just use Current, but whatevs).

You are welcome.

We Forge Our Spirits In the Tradition of Our NBA Ancestors

I’m under some measure of psychic stress right now that prevents me from writing coherently about anything that’s difficult to think about, which is most things. But I’m still capable of writing about basketball, so I’ll probably just do that for a while.

As regular readers of this space might know, the tens digit just rolled over on my personal odometer. In tribute to my ever-closer demise, I’d like to dedicate an indeterminate number of words to the deeds of the NBA’s current senior citizens. Every once in a while, I’ll select a baller of advanced years and write a sort of appraisal of their life and work. So if you care to know what I think about Ray Allen, Kurt Thomas (that’s right, he’s still in the league), Steve Nash, and other decrepit oldsters, and I know you do, keep your eyes on this blog. I’ll also tell you what I think about Jeremy Lin (spoiler: the whole thing irritates me to no end), the Washington Wizards (spoiler: they’re terrible… but how terrible?) and Bill Simmons (spoiler: he’s a raging sexist). It might not be nearly as fascinating as a discussion of why Saul Kripke’s puzzle about belief is actually no puzzle at all, but it should definitely fill any quota you might have for prolix posts about inconsequential shit. And who knows, you might even come back for the Kripke post.