1
votes

I started an Xcode project in 3.1 using Leopard. Then I took this project home to work on it over the weekend. At home, I have Xcode 3.2 on Snow Leopard. Since then, I have switched many times between developing this project on Leopard/3.1 and Snow Leopard/3.2. The project compiles fine on either setup. But, if I build on 3.1 (in release mode), the executable will not run in Snow Leopard. And If I build in 3.2, the executable will not run in Leopard.

My project settings are for 32-bit universal, base SDK 10.5, and the Release mode.

Any ideas?

2
I don't have any answer, I just wanted to say I share your pain wrt Leopard/Snow Leopard incompatibilities. - Pascal Cuoq

2 Answers

0
votes

Switching from leopard to snow leopard and back isn't good, because snow leopard doesn't work well with leopard and vice versa. To resolve this issue, upgrade both machines to snow leopard and the latest version of xcode. But before you do that, try cleaning your project first then compile.

0
votes

Here I will answer my own question, or at least, try to explain it.

I was transferring the Xcode project files from Leopard to Snow Leopard via DropBox (this problem also happened via a USB flash drive transfer).

When I tried to open the target application after moving through DropBox, the app wouldn't open. I opened the Console, and got a "posix_spawnp(blabla). Permission denied" So, it's a permissions issue. (sudo chmod a+x /username/Applications/AppName.app/Contents/MacOS/AppName would let me run the app).

I dunno if I need to fix permissions on my Dropbox folder on my local machine, or if it's a problem with the DropBox service.

But to transfer the app from Leopard to Snow Leopard, first I must zip the app and transfer the zip file via DropBox. Apparently, zipping preserves the permissions of the .app and doesn't let DropBox mess with it.