It used to be that "DaliClock" was one of the options on the Active Executable section of the Overview menu, along with "System Preferences" for DaliClockSaver. Now they are gone.
So, how do I fix this?
Update: I fixed it. Apparently I needed some combination of: deleting and re-installing XCode twice, and deleting my DaliClock.xcodeproj/jwz.pbxuser file and allowing it to be regenerated.
Did you try:
sudo /Developer/Library/uninstall-devtools --mode=allfollowed by a reinstall of Xcode yet? Sometimes this rubber-chicken waving helps.
I downloaded the project and tried it with Xcode 3.2.3 on 10.6.4. Seems to work (other than the fact that it couldn't find the base SDK, 10.4, which I don't think I installed). Once I changed the base SDK, it built and ran just fine. The iPhone target appears to run in the simulator correctly, too.
If you'd like to open a bug up on this and ping me with the radar #, I'll be happy to check into it at work tomorrow.
Alas, after waving that chicken, I still have no non-iPhone/iPad targets on the Overview menu.
XCode 3.2.3, MacOS 10.6.4, iMac8,1.
Changing base SDK to 10.5 and 10.6 had no effect (just to iterate available chickens.)
For what it's worth, this keeps happening. I have to delete the .pbxuser file and restart XCode three or four times a day or it stops being able to build non-iPhone targets. This is both before and after switching the project format to 3.2.
Would you mind filing a bug on this issue and attaching one of your error-inducing pbxuser files? Posting the bug number in a reply would be wonderful :-)
Project > Edit Project Settings > Build
and make sure that the right Base SDK is selected.
Did nothing.
I've been putting off upgrading to 3.2.3 until I can no longer hear my more eagerly-updating coworkers' moans and screams coming from their offices. It sounds like it's causing lots of people frustration. Deleting the pbxuser files might be the common solution here.
ugh. glad you fixed it!
It's not fixed, it keeps happening. I keep needing to delete that file and restart xcode.
ah didn't read the rest of the comments. XCode really is an abusive relationship.
Just upgraded to Xcode 3.2.3 (1688, allegedly) on 10.6.4.
Now, the SaVi satellite software I maintain is consistently randomly dying with segmentation faults and kernel errors, which it wasn't before on 10.5.x or 10.6.x. And that's just a trivial bit of userspace shell, Tcl/Tk and C.
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Application Specific Information:
objc_msgSend() selector name: release
Nice.
I believe Xcode 3.2.3's problems are not limited to iOS matters.