• 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: Building a framework within an app's project
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building a framework within an app's project


  • Subject: Re: Building a framework within an app's project
  • From: Tom McHale <email@hidden>
  • Date: Tue, 06 May 2014 14:00:24 -0700 (PDT)

Thanks, Quincey. I would do these steps before you add the framework with your steps above.

In the project you want to add the framework to collapse all the panes in project navigator.

In Finder drop the framework xcodeproj file into Project Navigator below the project already there.

Edit the scheme, select the Build (top row) item, then hit the '+' button. You should be able to add the framework project to the build.

Go back to Project Navigator and make sure the framework is above app. Drag there if it is not.

Build. This should build the framework then the app.

Now do what you described above. When you add  the framework to Build Phase you will see the project version of the framework there to choose.

Thx,
Sandip
On Tuesday, May 6, 2014 12:38 PM, Quincey Morris <email@hidden> wrote:
On May 6, 2014, at 12:17 , Tom McHale <email@hidden> wrote:


But when I do that I see foo.xcodeproj in the project navigator but it does not build when I build focuser. I must be missing something.

I think the problem is that you still need to tell the app project to use the framework. Go to the Link With Binaries build phase and click the “+” button. Select the framework from the resulting dialog.

This will add a framework item to the app project in the navigator pane. Once it’s there, I recommend you select it, and in the File inspector, set its path to “relative to build products”.

Finally, go to Search Paths in build settings, and make sure that Xcode didn’t add any paths (to the Frameworks setting) for your framework that mention the derived data directory. If it did, remove the setting — it’ll only mess things up at some point in the future — you normally don’t need an explicit build setting here.



 _______________________________________________
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

  • Follow-Ups:
    • Re: Building a framework within an app's project
      • From: Quincey Morris <email@hidden>
References: 
 >Building a framework within an app's project (From: Tom McHale <email@hidden>)
 >Re: Building a framework within an app's project (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: How to use the option key
  • Next by Date: Can't find the damn executable
  • Previous by thread: Re: Building a framework within an app's project
  • Next by thread: Re: Building a framework within an app's project
  • Index(es):
    • Date
    • Thread