> On Feb 17, 2015, at 9:07 AM, Dave <[email protected]> wrote: > > Why is it that Link Error produce a gibberish error message? It’s been like > this in XCode since as long as I can remember and I’ve often wondered why > they just don’t produce a decent meaningful error message.
It varies. Sometimes you get the real error message, and sometimes the iuild navigator just says the linker failed. :( There are a lot of cases where Xcode’s issue navigator either doesn’t show the real error message, or shows a whole ton of irrelevant cascading messages (like ‘lipo’ failures.) It’s just an annoyance to me, and I’ve written it off as one of the many flagrant bugs that will never ever get fixed, but I’ll bet it can be a real roadblock for new developers who haven’t learned how to read these tea leaves yet. There’s a delightful rumor that iOS 9 will be a no-new-features, just-improve-stuff release (like OS X 10.6). If so, maybe Xcode 7 will come along with it and just fix all the obvious bugs that have piled up over the years. Wishful thinking… > How can I figure what is wrong from this: That’s not the error message, nor even any of the output. That’s just the command-line that invoked the linker. The output, including the error, would come immediately after that. Also, the error output is usually visible before you flip open the raw-mode widget and see the entire gnarly command line, so normally you don’t have to scan through all that noise. —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]
