Got a few good search terms to respond to again, so here goes:
twiki install centos 5.1: Don’t do it unless you know what you’re getting into. I had a bad security experience likely caused by Twiki, and I’ve seen a lot of people reporting similar experiences that they are convinced was Twiki’s fault. At the very least, google “twiki security” before you do it. The codebase is much too large for a single person to audit it in a reasonable amount of time. If you need a good Wiki in general, give Moin a try. Consider using a Wiki hosting service, where someone else has to worry about the security of the underlying machine. Or just don’t use a Wiki at all — unless you truly want what a Wiki in specific has to offer.
iphone unofficial toolchain easiest way: There is no easy way. There is drudge’s way that I point to in another entry, but aside from that I didn’t find any way that was at all easy. binutils can be convinced to generate (possibly-working) tools for arm-apple-darwin fairly easily, but I think GCC is a bit trickier. Don’t try to do it on your own unless you want to spend a lot of time making the tools work rather than using them.
do peanuts have gluten?: Nope, peanuts don’t have gluten in them. They may have gluten on them, though — it depends on how they’ve been processed or flavoured. When in doubt, read the label and assume that “spices” includes something gluten-based. I’ve seen some with and some without gluten, so have a look around.
After realising that the iPhone/iPod Touch SDK isn’t going to do what I want it to do yet, I am experimenting with various ways of doing what I actually want to do — run programs on my iPod Touch, not a simulator.
My first try is drudge’s HOWTO build the toolchain on Leopard, and it looks good so far, which is to say that I’ve got “hello world” running on my iPod. It seems to include everything you’d need.
The next big question is how to package things up for installation onto the device. For now I’m going to assume that people can scp things to their device and ssh into it (or use a terminal) to do the installation. I will likely get the Installer packages built eventually, though.
Using xcodebuild I figured out the command line to build a simple “hello world” in C for the ARMv6 in my iPod Touch. After scping it into place it faulted on me with a bus error. I don’t know off-hand if the ARMv6 can actually raise a bus error, or whether that particular error is overridden to actually mean something else entirely.
I also have no way of figuring out if the executable is able to find its shared libraries, as otool is conspicuously absent on the iPod, and I don’t know how to check out ARM binaries on my Macbook. My guess at this point is that the Aspen 1.2 SDK will only generate executables for OS 1.2 and higher, so 1.1.3 won’t work.
So I got the iPhone/iPod Touch SDK downloaded and installed. Getting a sample app to run in the iPhone emulator is easy enough, but I can’t get it to run on my iPod Touch. There are two things I see getting in my way.
The first is that when I try to add an application to the iPod in the Organizer I get a message to the effect of “your mobile device has encountered an error” and the dialog specifies error code 34. I have no idea what this means yet, but I have a sinking feeling that it will only work with an iPhone, and not an iPod.
The second is that when I try to build the project for Aspen (as opposed to Aspen simulator) I get an error at the last minute about not having a code signing key. This I somewhat expected, but I also thought I should at least be able to put applications on my own device without having one. Typically, Apple is only allowing Americans to have code signing keys at this point, though they say that other countries’ developers will be included “in coming months”.
I’m feeling somewhat foolish for un-jailbreaking my iPod at this point. My only comfort at this point is that I’m not the only person struggling with it.
Update: The likely reason for this error is that the SDK builds code for OS 2.0.
Update: This seems even more likely, since programs built with the Apple SDK give bus errors when run on a device.
Update: If you want to get started building code that runs on a real device instead of the Aspen simulator, build a toolchain that will do the trick.
Unfortunately, it looks like the rumor mill was right. It’s almost as late in February as you can get (the 29th, no less) and there is no sign of the iPhone/iPod Touch SDK. Hot News has no details, and the ADC has no downloads listed.
Though I’m sure we’ll have it in our hands in good time I can’t help but think that Apple should have managed our expectations a little better, and perhaps told people it would be late. Keeping us guessing isn’t going to win them any friends and will do little to deter the hordes of people jailbreaking their devices.
It was phone upgrade time, so we took a look about and found a new phone for me that lets me kiss the days of my hundred-dollar data plan goodbye. The phone is a HTC Touch, and the going rate for unlimited wireless on it is CAD7 per month. I’m still not clear on exactly why it’s so cheap compared to the Q, but I’ll get it figured out.
In the meantime I’m going to try to blog when the urge hits, rather than waiting until the evening.
What do you get when you combine an iPod Touch, OpenSSH, Ruby, Vim, and a bunch of other useful stuff? One heck of a useful piece of hardware.
I’m looking forward to exploring Ruby on this new platform. I don’t have any clue how to build binaries for the platform (or even how to set up a cross-compiler that targets it), so it’ll be pure Ruby for now. I’ll have to see if RubyGems will work for pure-Ruby gems.