Re: "iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
Re: "iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
- Subject: Re: "iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
- From: email@hidden
- Date: Mon, 20 Jan 2014 18:57:49 -0500
This is an honest question as I don’t understand if they’ve actually created a framework, but it looks like it. Dropbox and TextExpander seem to have made frameworks of their SDKs that people can use. How did they do it?
Dave
On Jan 20, 2014, at 3:26 PM, Jens Alfke <email@hidden> wrote:
> Landon Fuller recently wrote a great blog post about the problems produced for third party developers (especially those who create libraries) by iOS's inexplicable lack of support for dynamic libraries/frameworks:
>
> http://landonf.bikemonkey.org/code/ios/Radar_15800975_iOS_Frameworks.20140112.html
>
> I am in full, vehement agreement. I complained about this topic here back in 2011 when I started at Couchbase and had to put a stupid amount of frustrating effort into trying to build and package a reusable code framework for iOS. (The eventual solution involved some really nasty Xcode hacks such as re-entrantly calling xcodebuild from a target build script. Ick.) Over the years since it's periodically consumed more of my time, and caused frustration for the developers trying to use our libraries (most recently when 64-bit iOS was introduced.)
>
> I've kept waiting for Apple to introduce some sort of improvement, or at least explain why the current situation can't be improved, but there's been nothing. Seems like it's time to raise the issue again and see if there'll be any better response … ?
>
> —Jens
>
>> When I first documented static frameworks as a partial workaround for the lack of shared libraries and frameworks on iOS, it was 2008.
>>
>> Nearly six years later, we still don't have a solution on-par with Mac OS X frameworks for distributing libraries, and in my experience, this has introduced unnecessary cost and complexity across the entire ecosystem of iOS development. I decided to sit down and write my concerns as a bug report (rdar://15800975), and realized that I'd nearly written an essay (and that I was overflowing Apple's 3000-character limitations on their broken Radar web UI), and that I may as well actually turn it into an actual blog post.
>>
>> The lack of a clean library distribution format has had a significant, but not always obvious, affect on the iOS development community and norms. I can't help but wonder whether the responsible parties at Apple -- where internal developers aren't subject to the majority of constraints we are -- realize just how much the lack of a clean library distribution mechanism has impacted not just how we share libraries with each other, but also how we write them.
>>
>> It's been nearly 7 years since the introduction of iPhoneOS. iOS needs real frameworks, and moreover, iOS needs multiple-platform frameworks, with support for bundling Simulator, Device, and Mac binaries -- along with their resources, headers, and related content -- into a single atomic distribution bundle that applications developers can drag and drop into their projects.
>> ...
>
>
>
> _______________________________________________
> 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
_______________________________________________
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
- Prev by Date:
"iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
- Next by Date:
Re: "iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
- Previous by thread:
"iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
- Next by thread:
Re: "iOS Static Libraries Are, Like, Really Bad, And Stuff (Radar 15800975)"
- Index(es):