• 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: Copying dependent frameworks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Copying dependent frameworks


  • Subject: Re: Copying dependent frameworks
  • From: Jerry Krinock <email@hidden>
  • Date: Tue, 22 Apr 2008 20:46:59 -0700


On 2008 Apr, 21, at 10:39, Doug Hill wrote:

On Apr 19, 2008, at 7:26 PM, Jerry Krinock wrote:

I then click the triangle and disclose the framework icon.

I don't understand which "framework icon" you mean.

When you click the disclosure triangle for a dependent project added to another project, you get an icon for the target that will be built. I'm guessing it references a target but could be something else like the built Product. In my case, I get an icon for the framework that is being built for the dependent project. I can drag this icon into the "Link Binaries" build phase and it will indeed link my app with that framework. And it will even link to the correct configuration of what I'm building (Debug vs. Release).

I see. I suspect this has the same effect as dragging the product out of the framework project.


However, dragging the icon to the "Copy Files" build phase doesn't do what I expect. I tries to copy a correct Debug vs. Release but from the wrong location. Specifically it is trying to find the framework in the main application build folder. Don't know why, which is why I was hoping someone on this list had some idea what's going on. Since I've gotten one other replies (which was someone who gave me a pointer to your website earlier)

Not sure if this is a problem, but in Xcode's Preferences ► Building, make sure you have set a Customized Location for your Build products. I've been told that things that don't work if you don't do that.


I ended up writing a script to copy the framework into the application bundle, but there are a couple of problems I have. Primarily my script doesn't know about the dependent project build status so it can't tell if the project changed or not. So it always does the copy no matter whether the dependent framework changed or not. Most of the time it's a useless step.

My script does the same thing. It probably takes about 10 milliseconds on a slow Mac. You and I probably spent 1000 * 10 milliseconds just writing and thinking about it, so you'll need to do lots of builds before getting a payback. Just let it go.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Copying dependent frameworks (From: Doug Hill <email@hidden>)
 >Re: Copying dependent frameworks (From: Jerry Krinock <email@hidden>)
 >Re: Copying dependent frameworks (From: Doug Hill <email@hidden>)

  • Prev by Date: Re: Xcode code sense
  • Next by Date: Re: thin linking: "file is not of required architecture"
  • Previous by thread: Re: Copying dependent frameworks
  • Next by thread: iPhone SDK, XCode, Unit Tests
  • Index(es):
    • Date
    • Thread