• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: gcc error paths in Organizer make builds
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc error paths in Organizer make builds


  • Subject: Re: gcc error paths in Organizer make builds
  • From: Fritz Anderson <email@hidden>
  • Date: Mon, 12 Oct 2009 15:21:37 -0500

On 8 Oct 2009, at 10:54 AM, Fritz Anderson wrote:

I seem to recall in 3.0 that if you used the Organizer as an IDE for makefile-based project, and gcc issued errors (or warnings), you could click on an error in the Build Results window, and see the problem line in the editor pane. I may be wrong, but that's what I remember.

Under 3.2, this no longer happens. I _think_ I see the problem: The make is recursive, gcc is invoked on a source path relative to the working directory, the error messages have no leading path information, and Xcode isn't comfortable guessing the path from just the file name.

Is there a way to get the behavior I remember? Is there a default I can set, or a gcc flag, or a customary make variable, that will put usable paths into the error messages?

May I renew this? Comments?

	— F

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >gcc error paths in Organizer make builds (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: Build Transcript
  • Next by Date: Static C++ lib under 10.5 and 10.6
  • Previous by thread: gcc error paths in Organizer make builds
  • Next by thread: Xcode 3.2.1 update is available in iPhone OS 3.1.2 SDK
  • Index(es):
    • Date
    • Thread