• 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: Dependency Checking Woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dependency Checking Woes


  • Subject: Re: Dependency Checking Woes
  • From: Scott Fraser <email@hidden>
  • Date: Fri, 17 Mar 2006 08:18:57 -0800

On Mar 17, 2006, at 03:44 AM, email@hidden wrote:

Perhaps something similar can be done in your case: have another
target that does nothing but touch one of your source files (a small
one, preferably) and have your main target depend on that. Every time
you press build, it should build one small file (mine is a two line
file containing two global variables, the date--in a particular
format--and the build number) and then link with your modified
libraries.

I used to do something similar in a multi-step MPW build script. The intermediate target could touch, not one of your source files, but a fake, empty source file that is part of your App target, and whose only job is to be touched. Sounds like it should work.


Scott
-----

_______________________________________________
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: Dependency Checking Woes
      • From: Rush Manbert <email@hidden>
  • Prev by Date: javadoc for xcode
  • Next by Date: Re: SVN addon for XCode
  • Previous by thread: Re: Dependency Checking Woes
  • Next by thread: Re: Dependency Checking Woes
  • Index(es):
    • Date
    • Thread