never turn your back on mother earth

[johnnyfavorite]

I told myself I couldn’t write this post until I had made actual money from this deal, proving that it is real. Today, the “federation of contractors” company direct-deposited money into my bank account, so that I can expedite my passport application. I think that counts

Comments

[agmsmith]

Not very oddly, I'm working on some iPad stuff at work. We finally got far enough to spring for a developer account, and after a couple of days of legal hoop jumping and trying to cram 2GB of RAM into an old Mac-mini with a metal spatula (the springy thin kind don't work as well as a stiffer one), I was able to sign and run code on a real iPad. Sample code, that is. Of course, our project didn't even compile when switching from the simulator to the real thing. I'll worry about that next week; now I've got a long weekend (Thanksgiving here) to work on the problem of what do you do with 25 pounds of Turkey?

Premature congratulations on finding a new working way of life, hope it works out!

[johnnyfavorite]

dude! that doesn't sound right! i have been doing ios programming for a couple of years now, and i can say for certain that i have never once had a program that would compile for the simulator, but not for the hardware. it is the same compiler in both cases, after all. the only conceivable way i could see that being possible is if you have an #ifdef somewhere that specifically targets the hardware/simulator divide.

on the other hand, it is very common for the code-signing part to fail. that only happens for hardware, not the simulator. are you sure that's not what you're seeing?

signed, a veteran of the ios wars

[agmsmith]

Yes, it's true, they're different. There's no for the iPad device, while there is for the simulator. It's probably moved around to some other place in the header hierarchy, I hope, since we need it for our file access wrapper.

[johnnyfavorite]

huh. well, i have done a fair amount of low-level file io in ios programs -- more than i should have, maybe -- but i can't recall having to #ifdef an include. guess you hit a part of the stack i haven't needed to use yet.