Code Monkey home page Code Monkey logo

Comments (4)

wcwynn avatar wcwynn commented on July 21, 2024

I successfully accomplished this recently. The way I did this was in exactly the same way as described here: https://github.com/jverkoey/iOS-Framework/#developing-the-framework-as-a-dependent-project

The key is to make sure that in your public framework's target you:
A) add target dependencies to your private frameworks and
B) link with the private libraries

Both of these can be configured in the Build Phases for your public framework (after you drag-and-drop the private frameworks into your public framework's project). The exact steps are detailed in the above link.

from ios-framework.

swgillan avatar swgillan commented on July 21, 2024

Were you able to get your framework created that way? I too would like to package up my framework which has a dependant framework in it. So far, following the steps, I can get it to build and create my public .framework, but if I add it to the app and build, I get an error saying it can't find the dependent header file.

I resolve this by adding the dependant .framework file to the app project folder as well, which removes that error. I would prefer to just have the one .framework file added to the project though.

from ios-framework.

wcwynn avatar wcwynn commented on July 21, 2024

Yes, it worked for me. I don't recall having the problem you mention but the advice I can give is to just try to make sure you've classified your headers correctly (public vs. project vs. private) in both the framework and also in the dependent framework. In my case, I was not attempting to access any headers in the dependent framework directly from my app (I was only using the dependent framework to implement functionality that was exposed in the outer framework that was used by the app). So if you're trying to access interfaces in the dependent framework directly from your app, that's not something I've ever attempted in the past. Hope this helps!

from ios-framework.

swgillan avatar swgillan commented on July 21, 2024

Thank you, that was indeed what the problem I was having turned out to be. I had my dependant framework referenced in the public header by app was using. Once I refactored things to remove that I was able to build the framework with dependant framework properly.

Thank you.

from ios-framework.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.