On 10 Feb 2009, at 10:15 am, Chris Hanson wrote:
Xcode will expand build settings in your Info.plist when it copies
it into your product.
This is a build setting that Xcode fills in by default when building
a target, not necessarily one Xcode provides UI for in the Build
tab. See the Xcode Build Settings Reference for the settings that
affect it and the settings it affects.
Understood.
I think I need to rephrase my question a little.
Having changed the name of the project/executable/target/prefix file
from the annoying and incorrect defaults that Xcode inserted based on
another of my projects (why??? - that question still stands), What
Xcode actually builds is correct. If I examine the package on disk
it's all fine, the executable name and info.plist all tie up correctly
and I can launch and run it in the Finder.
I was initially assuming it wasn't expanding the Info.plist properly
but that's not it after all.
It's when I try and launch the executable from within Xcode that it
persists in trying to execute a non-existent file at a path based on
the incorrect old name. I have tried Cleaning All and deleting the
caches but to no avail.
OK, just tried quitting Xcode and launching it again and it's working
now, so I guess that's fixed it. Grrrr!! I just wasted two hours on
this.
I would still like to know why Xcode persists in making me perform
this futile exercise every time I create a new project.
--Graham
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
