These keys are defined by CFBundle itself. Project Builder only provides a value for
CFBundleExecutable
. If you wish to use any of the other keys, define them in your
CustomInfo.plist
file. See the section Creating Bundles for information about creating a
CustomInfo.plist
using Project Builder.
CFBundleInfoDictionaryVersion . Used to support future versioning of the Info.plist format. It should be automatically generated by the development environment when you are building a bundle.
CFBundleExecutable
. The name of the main executable for the bundle. For an application, this is the application executable. For a loadable bundle it is the binary that will be loaded dynamically by the bundle. For a framework it is the shared library for the framework (in the case of a framework, the executable name is required to be the same as the framework name for launch-performance reasons). The executable name should not include any extension that may be used on various platforms (so an application bundle's executable name should not include the
.exe
on Windows.)
CFBundleIdentifier
. The unique identifier string for the bundle. This identifier should be in the form of a Java-style package name, for example
com.apple.foo.bar
. The bundle identifier can be used to locate the bundle at runtime as described below.
CFBundleVersion
. A Mac OS
vers
resource style version number. The value of this key can be a number, in which case it is interpreted as the unsigned long integer format defined by the
vers
resource on Mac OS 8. It can also be a string of the standard form "2.5.3d5". If it is a string, it is automatically converted to the numeric representation.
CFBundleDevelopmentRegion . The "native" region for the bundle. Usually this is the native language of the person who wrote the bundle. The development region is used as the last resort if a resource cannot be located for the user's preferred region or language.