• 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
Adding explicit dependency on Info.plist file for standalone executables
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Adding explicit dependency on Info.plist file for standalone executables


  • Subject: Adding explicit dependency on Info.plist file for standalone executables
  • From: Jens Miltner <email@hidden>
  • Date: Mon, 08 Mar 2010 12:25:04 +0100

Hi,

I have a couple of commandline tools that embed an Info.plist in the executable using the mechanism outlined at <http://developer.apple.com/mac/library/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html#//apple_ref/doc/uid/TP40005929-CH4-DontLinkElementID_6>.

Of course, since this done through a linker option, changes in the Info.plist will only end up in the executable if I actually link the executable.
Thus, if the only change I do is to the Info.pist, the tool won't be updated automatically when I build.
While at first, this doesn't look like a big deal, it becomes a big deal if using an automated build environment and there are numerous components to build...

Is there any way to define an explicit dependency on the Info.plist file for a tool target (e.g. similar to how I can define dependencies for shell script build phases)?

Thanks
-jens

 _______________________________________________
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

  • Prev by Date: auto-gdb
  • Next by Date: debug a forked PTY process
  • Previous by thread: Re: auto-gdb
  • Next by thread: debug a forked PTY process
  • Index(es):
    • Date
    • Thread