• 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: "Build" stops after first few errors.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Build" stops after first few errors.


  • Subject: Re: "Build" stops after first few errors.
  • From: Andreas Grosam <email@hidden>
  • Date: Tue, 6 Sep 2005 15:09:17 +0200


On 06.09.2005, at 00:20, Markus Hitter wrote:


Am 05.09.2005 um 23:28 schrieb Adam Knight:

This should give you a better idea of why the answer is no:

    http://gcc.gnu.org/ml/gcc-help/2002-01/msg00253.html

You could file a bug report(1) with Apple (like I just did) to get Xcode to move into each dir and run gcc locally on every file, though. Maybe an option in XC3.

Better yet, gcc should be run from the root level of the project (and be given paths relative to there). The directory the .xcodeproj file lives in, I mean.
XCode changes to the directory where the xcode project is located - however, the source file which is to be compiled is (might be) passed with an absolute path.

I'm not sure, if the path specification for XCode's Groups and Files (relative to ..., absolute) may affect the command line, though.


But rather than choosing the path to the xcode project (this is where SRCROOT points to per default), I would prefere the *root to the project sources* - which is not necessarily the same path.
There is no build setting variable for this path - so XCode can't determine this path anyhow, hence will be unable to take it into account when generating the command line.



My experiments setting SRCROOT manually (to which the doc says, "this is usually not directly modified by the user"), didn't have any effect, apparently. Unfortunately, the doc says little about SRCROOT - so I would appreciate additional information.




Andreas


The file name solely can lead to wrong readings if you have more than one file with the same name. The upper part of the full path isn't interesting either.


This would make the build transscript much more readable as well ...


Markus


- - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/




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


This email sent to email@hidden


_______________________________________________ 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
  • Follow-Ups:
    • Re: "Build" stops after first few errors.
      • From: Markus Hitter <email@hidden>
References: 
 >"Build" stops after first few errors. (From: Jonny Taylor <email@hidden>)
 >Re: "Build" stops after first few errors. (From: Adam Knight <email@hidden>)
 >Re: "Build" stops after first few errors. (From: Markus Hitter <email@hidden>)

  • Prev by Date: Re: Debug/Release Library Matching
  • Next by Date: Re: "Build" stops after first few errors.
  • Previous by thread: Re: "Build" stops after first few errors.
  • Next by thread: Re: "Build" stops after first few errors.
  • Index(es):
    • Date
    • Thread