• 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: Xcode dependency handling
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode dependency handling


  • Subject: Re: Xcode dependency handling
  • From: Douglas Norton <email@hidden>
  • Date: Sat, 3 Feb 2007 19:40:43 -0800


On Feb 3, 2007, at 3:15 PM, Chris Espinosa wrote:

On Feb 3, 2007, at 1:49 PM, Mark Hamilton wrote:

The headers are all in the same directory as the C files, and they are members of the project. However, your second comment is probably the problem. Silly me, since  I have software update turned on I assumed that XCode would have been updated too, I'll try updating that and see is that improves things. Thanks.

Well,  upgrading to XCode 2.4.1 didn't fix the problem. I can add an intentional error to my .h file and build, and it doesn't compile anything. All of my .c and .h file are in the Sources folder, and clearly when the files are compiled the compiler finds the .h files so the -I's on the command line are correct. Anyone have any thoughts, or suggestions on where to look?

When I asked "relative to the project" I meant is the project arranged like this:

ProjFolder
  Proj.xcodeproj
  Sources
      myclass.m
      myclass.h

Or like this:

ProjFolder
   ProjectFile
       Proj.xcodeproj
   Sources
       myclass.m
       myclass.h

Because there's a known bug with dependency analysis with layouts like the latter.

What would help is to file a bug report with a full build transcript, and perhaps a copy of your project file (we don't need the sources.)

Chris

Mine is the latter, as I share some common library sources with a Windows VS2005 project

MyProject ƒ
WindowsStuff ƒ
Window specific source ƒ
headerThatIsNotSaved_WindowsImp.cpp
VS2005.solution
MacStuff ƒ
Mac specific source ƒ
headerThatIsNotSaved_MacImp.cpp
Xcode.xcodeproj
XPlatform ƒ
XPlatformSource ƒ
Headers ƒ
headerThatIsNotSaved.h

Scratch up another victim. If the option in the prefs caused Xcode to save _all_ files, regardless of which project it thinks they belong too, my issue would be resolved.

After all, if I save files from another project I did not want saved at that moment, Time Machine will be my saviour, as will my source control database :).

Douglas


 _______________________________________________
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: Xcode dependency handling
      • From: Chris Espinosa <email@hidden>
References: 
 >XCode dependency handling (From: Mark Hamilton <email@hidden>)
 >Re: XCode dependency handling (From: Chris Espinosa <email@hidden>)
 >Re: Xcode dependency handling (From: Chris Espinosa <email@hidden>)
 >Re: Xcode dependency handling (From: Mark Hamilton <email@hidden>)
 >Re: Xcode dependency handling (From: Mark Hamilton <email@hidden>)
 >Re: Xcode dependency handling (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: Automatic versioning
  • Next by Date: Re: Xcode dependency handling
  • Previous by thread: Re: Xcode dependency handling
  • Next by thread: Re: Xcode dependency handling
  • Index(es):
    • Date
    • Thread