Skip to main content

Bundle Name, Executable Name, Product Name…anything else?



Bundle Name, Executable Name, Product Name... any more??





can someone please help clarify the use of each of these in Xcode on an iPhone project? They never fail to confuse the living bajezus out of me...and Im tired of getting them wrong.





Someone please explain... why the hell do we need this many different naming schemes for one app environment? and what do I use each of these for so I can stick them in the right cubby hole in my head?


Comments

  1. If you look at an info.plist, it goes something like this:

    Bundle Display Name - ${PRODUCT_NAME}
    Executable File - ${EXECUTABLE_NAME}
    Bundle Name - ${PRODUCT_NAME}


    So you can see, that normally PRODUCT_NAME gives you the same name for the bundle and what the user sees.

    In some cases you may want a more complex display name that is not suitable for naming things like bundles or executables, which is why you can change them independently - but you don't have to. The default it that PRODUCT_NAME is the same name as the project name, but you can also override it in the build settings.

    You shouldn't be changing the way they are set up in info.plist, unless you have a very good reason... just change PRODUCT_NAME.

    ReplyDelete
  2. Bundle name - is folder name, where your app (including executable file and all resources) will be stored (Cool Program.app).
    Executable name - is a program binary name, i.e. Cool Program.app/CoolProgram
    Bundle display name - is what will be shown on iPhone screen, for example Cool Prog (since Cool Program probably will not fit on Springboard).
    And, Apple claims, that Bundle Display name must correspond to Bundle name, i.e. you cannot use bundle name TheApplication, and bundle display name Something Other

    ReplyDelete
  3. According to Apple.com docs, it's exactly the opposite of what you'd expect.

    The "Display name" is the ACTUAL name of the bundle.

    But the "Bundle name" is just the short "DISPLAY" name.

    Actual cut/paste from Apple.com:


    CFBundleDisplayName (Recommended, Localizable) The actual name of the bundle.

    CFBundleName (Recommended, Localizable) The short display name of the bundle.


    Ugh.

    ReplyDelete
  4. When you have a application with UI(eg: Calculator) then most of the above will be same and doesn't matter much but if your project output is just a bundle(some engine) then you can have different executables(apps/frontend with UI which uses ur bundle as backend) of your bundle that you can specify using different executable name. And ideally as Kendall said bundle name will be same as product name. Refer Xcode Build System Guide for better understanding. Hope this helps. :-).

    ReplyDelete
  5. Out of those 4 variables, BUNDLE DISPLAY NAME is the only 1 that still makes sense.
    (Even after all the explanations given.)

    Maybe this will help:
    Which of those 4 have to be unique, when we submit something to the app store?

    Can I have the same "executable name" as an app that already exists in the store?
    (As long as my "Bundle Display Name" is different?)

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex