Update for iOS6 and armv7s? about ios-framework HOT 10 CLOSED

Agreed. There are a few points in Xcode 4.5 where the (well-written and clear!) directions hit a wall.

from ios-framework.

Interesting. I thought I had made it work for ios6 and armv7s. Forgot about this and would have closed it if I remembered to.

What issues did you run into? Would love to know so I can update appropriately.

_EDIT_ WHOA. I must have been completely out of it when I made this comment. I thought this was on a ios library that I maintain for filepicker.io. I did not submit a patch nor did I get this working for xcode 4.5. I used in on an older xcode and it still works. Sorry about that. But I hope someone can help out.

from ios-framework.

Okay, I'll start over again, making a framework (called "VideoWorks") in Xcode 4.5:

. In "Create the static library target", step 2, making the initial header "public", the option is not in the Utilities pane. In Targets --> Build Phases, I can "Add Build Phase" --> Add Copy Headers, where I can then put the header in the public section. (This then gives me the option to change it in Utilities pane!)

. In step 5, the folder structure it generated for the framework was correct, but one level up was different:
Debug-iphoneos/
VideoWorks.framework/
(as it should be)
VideoWorksHeaders/
VideoWorks.h
include/
VideoWorks/
VideoWorks.h

. In "Creating the Framework Distribution Target", step 4 "Build and Verify", the product ("libVideoWorks.a") is red, and does not show in finder. Inside the products folder though, there is the VideoWorks.framework folder.

. In "Resources and Bundles", Step 1 "Create the bundle target", the Choose Options are slightly different, such as the "Automatic Reference Counting" checkbox. (I said yes)

. In "Developing the Framework as a dependent product", Step 1 "add the framework project to your application project": if I make a new project, and drag the VideoWorks.xcodeproj into the new project's frameworks folder, I get only the blue VideoWorks.xcodeproject name, none of the subfolders shown in your screenshot. This makes the rest of the instructions here moot.

. I'm still able to add the framework to my test app, as outlined in "Adding the framework to a third-party application", though I am getting errors:

"ld: framework not found VideoWorks
clang: error: linker command failed with exit code 1 (use -v to see invocation)"

This could still be my error somewhere along the way - I'm investigating it further.

Thanks for reading!

• rick

from ios-framework.

I have the same issues, the missing (red) .a file, and the framework folder that exist even though it should look different according to instructions.

from ios-framework.

See this stackoverflow question for a solution to the inability to add a dependent project:

http://stackoverflow.com/questions/5373192/adding-project-as-dependency-in-xcode-4-x

from ios-framework.

I also have problem with including framework in third-party application (under XCode 4.5 and iOS 6).

"ld: framework not found FrameworkName
clang: error: linker command failed with exit code 1 (use -v to see invocation)"

Does anybody solved this issue?

from ios-framework.

I also have the same problem. "ld: framework not found FrameworkName". I'm also confused by what to do with the .a file. Do i distribute that separately? or add it to the .framework? or do nothing with it?

Xcode 4.5.2

from ios-framework.

Got it: make sure you select your aggregate target in the build schemes. Then your lib will build and you can add the framework to a third party app without errors. For the problem with dependent products: just close the other project and it'll work, too.

from ios-framework.

I just spent some time walking through the instructions yet I am also seeing the "ld: framework not found ..." error. Can someone elaborate what "make sure you select your aggregate target in the build schemes" means? In my aggregate, I do have my "Target Dependencies" defined within the "Build Phases" tab. I'm not sure if that is suppose to mean the same thing.

I'm able to get the Serenity/Third Party to work fine. What I'm confused about is the structure of the .framework directory. When I add my framework to my application, where does the guts of the library live? For example, Serenity looks like this on my machine:

Headers -> Versions/Current/Headers
Serenity -> Versions/Current/Serenity
Versions

The 2nd entry, 'Serenity' is a broken link.

from ios-framework.

Closing this barring any further updates. Please reopen if this issue is still active.

from ios-framework.