• 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: Automate build numbers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Automate build numbers


  • Subject: Re: Automate build numbers
  • From: Michael Wladarz <email@hidden>
  • Date: 31 Aug 2006 11:06:00 +0200

Hi all,

I try to include the perl script from http://www.red-sweater.com/blog/?p=23#finalscript
It works fine but how to ignore the "M" behind the revision number?

Thanks Michael

On Samstag, 26. August 2006 8:01 Uhr, Chris Espinosa <email@hidden> wrote:
>
>
>On Aug 25, 2006, at 5:41 PM, Jerry Krinock wrote:
>
>YES! That worked!  Very strange.  So, as you can see from the final, working
>Info.plist file which I've pasted in below, the things that Xcode replaces
>DO want the ${...}, but the things that the gcc preprocessor replaces do NOT
>want the ${...}.  Intuitive!!
>
>
>Now I understand why Apple hasn't gotten around to writing any detailed
>documentation on this.   I think I'll go clean my garage....
>
> So there are two separate mechanisms in Info.plist
>preprocessing, both added at developer request:
>
>
>
>- a way to substitute Xcode build settings in plists
>- a way for plists to expand C macros from #include files
>
>
>Both are valid and useful, but they have to be a) consistent
>with their natures and b) separable from each other so they
>don't step on each other.
>
>
>Xcode build settings are always expanded with the
>${SETTING_NAME} notation, and C macros are always expanded
>wherever found in the text.  
>
>
>This may not be "intuitive" to you, and its documentation is
>indeed sparse (see "Preprocessing Info.plist Files
>at http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeUserGuide/Contents/Resources/en.lproj/05_02_bs_targets/chapter_30_section_6.html),
>but if you have suggestions on how to support both of these
>different mechanisms in a more intuitive way, please file an
>enhancement request at http:/bugreporter.apple.com
>
>
>Chris
> _______________________________________________
>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
>


 _______________________________________________
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: Automate build numbers
      • From: Johan Kool <email@hidden>
  • Prev by Date: Adding images in IB
  • Next by Date: Re: Automate build numbers
  • Previous by thread: Re: Automate build numbers
  • Next by thread: Re: Automate build numbers
  • Index(es):
    • Date
    • Thread