• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Embedded frameworks and hard links
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Embedded frameworks and hard links


  • Subject: Re: Embedded frameworks and hard links
  • From: Ashley Clark <email@hidden>
  • Date: Thu, 25 Feb 2010 00:21:11 -0600

On Feb 25, 2010, at 12:12 AM, Stephen J. Butler wrote:

> On Wed, Feb 24, 2010 at 10:58 PM, Ashley Clark <email@hidden> wrote:
>> I've manually replaced the contents of the duplicate framework in the action with hard links to the other embedded framework and it works well but I'm wondering if there's some automated way to do this already that I'm missing.
>
> There was a thread on Darwin Dev about directory hard links awhile
> ago. An apple employee jumped in to say that:
>
> "You're not supposed to notice that directory hard links are now
> allowed (for Time Machine's exclusive use) so it's neither an error in
> the documentation or an error in the function.  The error is that
> you're being too nosy. :-)"
>
> Indeed, the man pages for ln and link(2) say it's not allowed. So
> whatever route you go to solve this problem, don't hard link
> directories. Beyond the normal  problems with such things, I'd be very
> suspicious that they copy/archive properly in all situations (which
> would negate your space savings).
>
> Either try what Sherm Pendley suggests, or maybe just use relative
> symbolic links.

Well, I was only hard linking the files within the frameworks since I knew that although directory hard links existed, they weren't available outside of TM.

I've since added the (much longer) @loader_path/../../../../../Frameworks to my runpath search paths for the Automator action (since I'm using @rpaths) and am now removing the frameworks in a build step after the action is embedded. This seems to work well in my case.

As long as I don't screw up the script and wipe out my hard drive. ;)
Always a little nervous automating file deletions.


Ashley



_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Embedded frameworks and hard links (From: Ashley Clark <email@hidden>)
 >Re: Embedded frameworks and hard links (From: "Stephen J. Butler" <email@hidden>)

  • Prev by Date: Re: Embedded frameworks and hard links
  • Next by Date: NSColorPanel changeColor not called
  • Previous by thread: Re: Embedded frameworks and hard links
  • Next by thread: NSColorPanel changeColor not called
  • Index(es):
    • Date
    • Thread