Friday, May 18, 2012

title pic Attention Mac Heads

Posted by pookzilla on May 25, 2005

The end of 3.1 is seeing a lot of effort directed to fixing certain polish issues.  One such issue is that we’d like to ship the OS X build such that the eclipse folder has a custom icon.  This is described in bug 95353.  This is proving problematic, however.  The OS X build is built on a non-OS X platform and we’re having a real problem trying to package a folder such that the OS X resource forks are maintained.  Anyone have any ideas how we might accomplish this?


Filed Under: Eclipse Comments: 2 Comments to Read

  • Michael said,

    I’m not entirely sure how to do this either – but I do know that resource forks can be represented on non-HFS disks using the dot-underscore file prefix:


    http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Concepts/FilesAndFinder.html

    The documentation on bundles might also be appropriate…?


    http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFBundles/Concepts/BundleAnatomy.html

  • Philippe said,

    the .DS_Store is transient and would be lost during a copy. Adding manually is not an option.
    Normally an Icon file is created under a folder when a custom icon is attached to it, but the .DS_Store is also updated. Just dropping the icon in the folder does not seem to be enough…
    I guess the bundle route would be the way to go.

    What about making the top level eclipse directory a bundle?
    (ie renaming the top eclipse folder to eclipse.framework or eclipse.app or set the bundle bit)

    I do not know how to set a bundle bit on a folder, and do not know if that would be preserved with a tar.

    They can include only resource files if needed and do not have to be executable so a framework may be more appropriate.
    With its own Info.plist pointing to an icon file and looking something like that …(see bug as I cannot paste Xml in that blog :-(
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=95353

Add A Comment

top