• 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: Derived file dependency tracking?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Derived file dependency tracking?


  • Subject: Re: Derived file dependency tracking?
  • From: Ethan Tira-Thompson <email@hidden>
  • Date: Tue, 30 Jun 2009 14:57:28 -0400

Further information: if using "Method B", where i use a "Run Script" build phase, I realized if I add the derived header file to the project, then I get the same behavior as in "Method A". In other words, dependent source files will be updated on secondary builds, but not on the original build where the header was updated.

Aside from not working, this approach is also problematic because it requires me to add a file to the project which doesn't even exist yet when first adding the '.fsm' file. But it may be of interest from a diagnostic point of view. Ideally, I don't think this step should be necessary even if it did work. :(

thanks,
  -Ethan

_______________________________________________
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: 
 >Derived file dependency tracking? (From: Ethan Tira-Thompson <email@hidden>)

  • Prev by Date: Re: GC pros and cons
  • Next by Date: Re: GC pros and cons
  • Previous by thread: Derived file dependency tracking?
  • Next by thread: Building a Static Library for iPhone and Simulator
  • Index(es):
    • Date
    • Thread