> On Jun 25, 2015, at 12:35 PM, Tony Scaminaci <[email protected]> > wrote: > > I hate bashing Xcode since I use it on a daily basis but there are other > weird things happening such as Xcode throwing errors when compiling a > command-line app that builds and executes fine using gcc, g++, and/or clang > and a Makefile.
What does “throwing errors” mean here? At first I thought you meant throwing exceptions — that Xcode would crash or display some fatal-error alert — but from what’s below I don’t think that’s it. > When I see anomalies like this, I wonder how reliable Xcode is. If a program > builds and executes on multiple linux, PPC, and Intel platforms with gcc, > g++, and clang (as appropriate for the platform) yet can't compile when > sucked into Xcode, how do I debug this? So you’re talking about compile errors. It would help if you posted an example. > One recurring error is Xcode failing to find externally declared functions in > an included header file. This is probably a clang problem Actually it sounds more like a problem with the search paths in your project configuration. Seriously, I use Xcode a lot, building Obj-C, C and C++, and only extremely rarely do I run into any actual compiler bugs. Maybe one a year or so. (Swift is a different matter, but that’s kind of to be expected given how new it is.) Build errors, yeah, a lot, but they almost always turn out to be something wrong in the build settings. —Jens _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
