First version of QtPersistence released
So, awhile back, I asked about an ORM framework for Qt. I didn't find much else in that category, and nobody else had any thing that was feasible either. I appreciated the suggestions about QDataStream, the XML stuff the Kadu folks are doing, etc, but I really wanted a database - perhaps because I'm crazy like that. 
Anyways, I spent about 6 weeks of spare time, and started the QtPersistence project - which is releasing it's first version today - and because I'm blogging about it, it's now official.
The release notes are here and the tarball is here. I'll probably do another release in about two weeks that does a better job of setting up various bits of project infrastructure but I got something that works passes its test suite, so I'm putting it out there. As always, constructive feedback is welcome.
Update: I left out the most important thing! The source code repository is on Gitorious at http://www.gitorious.org/qtpersistence
i can haz object persistence with Qt?
ok, so before i spend time going and creating something totally awesome to do object persistence with Qt, I have a question.
Have people already done something like this?
What I Know:
I know about Kandau already. I looked at it, and it's Qt/KDE 3 only, and I don't really want to spend the time to port it to Qt/KDE 4, mostly because I didn't like the way you had to use it.
I'm not too interested, at the moment, in using the Ruby bindings to Qt (which would then give me access to DataMapper and/or ActiveRecord), but depending on what's out there, I may go that route anyways.
Akonadi:
Before somebody suggests Akonadi (which is awesome), it doesn't really fit my use case at the moment. I'm looking for something pretty simple, and I'm not concerned with exporting data to other apps right now.
devenv 1.0 released
Just made the first release of a small project of mine that I wrote to handle my various projects and development environments. It's called devenv and the homepage is at Gitorious. 1.0 is the "it works good enough for me so here it is" release. It's designed only for zsh, so if you try to run it on not zsh, it will crash and burn.
Would love some feedback, patches, etc. Future ideas include commands/scripts for updating source trees for a project, doing a better job of handling branches, and anything that I notice that I start to do a lot that will keep me from typing, cause I'm lazy.
figure out where your build errors are
I'm fortunate enough, both at work and at home, to have multiple machines to distribute my compiles to. This means I'm generally using something like 'make -j5' or 'make -j10' to build stuff with. However, a lot of times, especially now with cmake, I'm not completely sure what exactly caused my build error when I have one. The trick that i've started using is running 'make -i -j10' first - which means make builds the whole tree and doesn't stop on errors - and then going back and doing a single 'make' to figure out what didn't compile.
Perhaps I'm late to the party with this, but since it's been rather useful for me, so I thought I would share.
OS X and Icecream, a yummy combination!
I've been spending most of the last three days trying to figure out how to get a cross compiler built so that I can use my mac in my icecream compile cluster here at the house. SUSE provides some nice packages for boxes that run linux, but I had to make one for the mac. I'm pleased to say that I've succeeded. I used Dan Kegel's nice crosstool script to build the compiler and used the instructions from the icecream at the opensuse wiki to create the tarball and that was pretty much all there was to it.
Now, I did have some difficulty earlier with trying to use a newer glibc version (i wanted to use the same one as on the suse box). since you're not linking against it anyways on the mac, i went with an older, actually tested version and all was fine from there.
Now, it's off to go make my desktop useful for hacking again.