3 ms·
Classic linking uses a path to a library at link time. I suppose Apple may have patched ld to work around this choice, but it still begs the question — why cha
by loeg 6y ago
Classic linking uses a path to a library at link time. I suppose Apple may have patched ld to work around this choice, but it still begs the question — why change this? Who was it hurting?
- pjmlp 6y agoNot in every OS or programming language, it doesn't. Linkers just need to somehow find the binary dependencies across the link path/staging.
- saagarjha 6y ago> why change this? Who was it hurting? Performance.
- oneplane 6y agoAnd security. If you sign a single cache across millions of systems you know that that is the one true non-tampered cache.
- loeg 6y agoCan you elaborate beyond a single word? It is certainly not immediately obvious to me how this benefits performance, or I wouldn't have asked.
- saagarjha 6y agoHere's one optimization: http://sealiesoftware.com/blog/archive/2009/09/01/objc_explain_Selector_uniquing_in_the_dyld_shared_cache.html http://sealiesoftware.com/blog/archive/2009/09/01/objc_expla...
- saurik 6y agohttp://www.cydiasubstrate.com/id/727f62ed-69d3-4956-86b2-bc0ffea110c1/ http://www.cydiasubstrate.com/id/727f62ed-69d3-4956-86b2-bc0...
- bdash 6y agoThe Apple linker has used `tbd` files, a textual description of a dynamic library's interface, rather than actual dynamic libraries at link time for iOS for several years now. Prior to that it was using stub dylibs, which were essentially symbol-table-only dylib files.