Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
kylesow said:
I dragged the executable into terminal and it worked. I guess I'll just do that until I can find out whats wrong with Xcode. Thanks for the help.

It makes me sad that this problem bousozoku noted is so widespread :(
 
Works consistently here

This works fine for me on OS X 10.3.3 - Xcode 1.1:

Code:
C++ is power programming.
Testing has exited with status 0.

That is the actual output from the "Run" window. I opened a new Tool-C++ project, which had functionally identical code as the original post, copy/paste the original "problem" code and clicked Build and Go.

I think there may have been an issue with creating the original project that caused the problems. The different project types all have special settings to build the resulting targets, its not like they all have the same steps or parameters. Don't use "Empty Project" unless you know what you are doing (as far as your particular project's requirements).

BTW I have never had problems getting output in Xcode or Project Builder via printlining.
 
encro said:
It makes me sad that this problem bousozoku noted is so widespread :(

It doesn't please me at all, either. I tend to use the IDE's editor just for the syntax highlighting and compile and run at the shell prompt--well, just for non-GUI applications.

jGrasp from Auburn Univ. is a good IDE--it's lightweight, supports C, C++, Java, and Objective-C, so anyone interested might try that instead. Eventually, Apple will get it worked out.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.