Re: Question about Info.plist's

Thanks a lot for everyone's insights and suggestions! For the record: I have now shed a bit of old baggage in my code. (I did the version management and the build number incrementing too cumbersome; I must have picked up the CFBuildNumber somewhere 14 years ago ...) Anyways, I am now using the C

Re: Question about Info.plist's

> https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-102364 > : Thanks a lot! The CFBuildVersionNumber seems to be very restrictive :-( """ While developing a new version of your app, yo

Re: Question about Info.plist's

I can send anyone who wants it my two projects that increment build numbers if you’re interested. Just let me know. Alex Zavatone > On Aug 19, 2020, at 9:45 PM, Michael Hall via Cocoa-dev > wrote: > > > >> On Aug 19, 2020, at 9:04 PM, Michael Hall wrote: >> >> >> I’m not familiar with t

Re: Question about Info.plist's

> On Aug 19, 2020, at 10:04 PM, Ben Kennedy wrote: > > >> On 19 Aug 2020, at 7:45 pm, Michael Hall via Cocoa-dev >> wrote: >> >> Something else I’m curious about is doesn’t this somehow invalidate any >> application signing that’s been done? > > Code signing happens last, even if you put

Re: Question about Info.plist's

> On 19 Aug 2020, at 7:45 pm, Michael Hall via Cocoa-dev > wrote: > > Something else I’m curious about is doesn’t this somehow invalidate any > application signing that’s been done? Code signing happens last, even if you put your shell script phase at the very bottom. (Observe the build outp

Re: Question about Info.plist's

> On Aug 19, 2020, at 9:04 PM, Michael Hall wrote: > > > I’m not familiar with the Plistbuddy that’s been mentioned. I see that is in fact builtin. Wasn’t aware. Something else I’m curious about is doesn’t this somehow invalidate any application signing that’s been done? ___

Re: Question about Info.plist's

> On Aug 19, 2020, at 11:07 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > Question: > > Is there a way to use a key/value that was defined earlier in the plist file > to define a value for a later key? > Maybe off-topic but this used to be supported for Java applications for pre-set vari

Re: Question about Info.plist's

> On 19 Aug 2020, at 11:47 am, Gabriel Zachmann via Cocoa-dev > wrote: > > I tried this: > > plutil -replace CFBundleVersion -string '$(CURRENT_PROJECT_VERSION) 111' > qq.plist > > which works -- but what I need to do is something like this: > > plutil -replace CFBundleVersion -string "\$

Re: Question about Info.plist's

Thanks a lot for the insights. > On 19. Aug 2020, at 18:44, Glenn L. Austin wrote: > > No, you can't use an "earlier" key to create a "later" value - but you can > use code to do basically the same thing. > > Or, you can use the same variable that sets your CFBuildNumber to set your > CFBundl

Re: Question about Info.plist's

> On 19 Aug 2020, at 9:07 am, Gabriel Zachmann via Cocoa-dev > wrote: > > The plist file has, additionally to all the default stuff, the key > CFBuildNumber (with a value that I increment automatically). > > In Xcode, I tried to change "Bundle version" to a value like > > $(CURRENT_PROJEC

Re: Question about Info.plist's

On Aug 19, 2020, at 11:11 AM, Saagar Jha via Cocoa-dev wrote: > > Which file are you modifying? The one in your source directory? Because the > one that goes in the final product doesn’t get copied over until after you’ve > lost most control over the build process (it’s done by Xcode after the

Re: Question about Info.plist's

Which file are you modifying? The one in your source directory? Because the one that goes in the final product doesn’t get copied over until after you’ve lost most control over the build process (it’s done by Xcode after the normal build stages). > On Aug 19, 2020, at 09:58, Owen Hartnett via C

Re: Question about Info.plist's

You can also use a build script that calls PlistBuddy to alter the contents of a plist called using a Run Script in Build Phases just before Compile Sources. I used to use one to apply the subversion revision number to the build version, but then I switched to git. -Owen > On Aug 19, 2020, a

Re: Question about Info.plist's

No, you can't use an "earlier" key to create a "later" value - but you can use code to do basically the same thing. Or, you can use the same variable that sets your CFBuildNumber to set your CFBundleVersion. -- Glenn L. Austin, Computer Wizard and Race Car Driver <><