-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error building: product type 'com.apple.product-type.framework.static' #1
Comments
Hi, the sample app actually has a dependency on the BDApplicationHelpers framework target that is included in the project. In order to build the BDApplicationsHelpers framework, you need to use Karl Stenerud's great iOS-Universal-Framework script files. https://github.com/kstenerud/iOS-Universal-Framework download or git the project and run the scripts in the "Real Frameworks" folder. Let me know how this works. |
That got me past the error above. Then I got this (odd) error:
I added a cast to
Then I ran into a bunch of dependencies on
Missing:
|
Thanks for helping out with the project. I had not compiled the project with xCode 4.4.1 yet. Yes the issue with the return nil is interesting. I will fix and push the change to repo. In regards to the missing resources, the issue is the reference to the BDApplicationHelpers.embeddedframework in your project. Delete the reference that you currently have and find the embeded framework in your products folder. Drag and Drop it on back in the applictionHelpers sample project target. Note, that I just downloaded the project, and I seem to be getting a DTrace error having to do with one of the files. I am still trying to track down the root cause for that. |
I did this. I also removed the missing resources from the Copy Bundle Resources list, and this allowed the app to build. I had to re-add the With the exception of the Help button, the app seems to be working correctly for me. |
I traced the overall issue back to XCode4.4 upgrade as well as the upgrade not playing nicely with the iOS-UniversalFramework scripts. I've completely updated the project and pushed it to the repo. Instead of the sample app being dependent on the framework being in the build directory, I have placed a copy of the framework in the applicationHelpers sample app directory. This will mean that everytime a change is made to the framework, users will have to paste the update framework back into the appropriate directory. If you are good with scripting Xcode it would be helpful for this automatically to get done. Try downloading the repo again. It should work. Thanks for the help. |
Yes, it works. Thanks! There is still one minor issue. When I compile I still get the following warning, which can be fixed by editing applicationHelper's Framework Search Paths:
I'm not clear as to whether it's still necessary to install the iOS-Universal-Framework to run the test app, but if it is I would recommend calling that out more explicitly in your README.mdown (it's only mentioned in the credits section). I came to your project from your answer to http://stackoverflow.com/questions/8146253. I'm trying to understand how to implement a container view controller, and I think that looking at your code is going to help. Thanks again. |
howdy. based on your feedback, I'm going to modify the project a little bit to remove that dependency. Truth be told, you could just add the BDApplicationHelper source files and the associated headers and link it that way. I wanted BDApplicationHelpers to be a framework to be used in other apps that I am working on. For a more simple intro to viewController containment, check out https://github.com/toolmanGitHub/stackedViewControllers |
Sorry for my ignorance, but when I try to build BDApplicationHelpers under Xcode 4.4.1 I get the error:
The text was updated successfully, but these errors were encountered: