News for hackers. Stuff that matters.
Re:Announcing Rust 1.16 by eridius on Thursday March 16, 2017 @04:48PM (#13889031)
AFAIK the only difference between a dylib and a framework is the folder structure (and I guess the install path of the library). So in theory you could produce a cdylib, create a framework folder structure for it, and then use install_name_tool to update the install name appropriately.
Re:Announcing Rust 1.16 by conradev on Thursday March 16, 2017 @06:59PM (#13889932)
That's what I thought, too, but I was reminded of the filetype field in the mach_header which has distinct MH_DYLIB and MH_BUNDLE values. fwiw, I don't think that difference means much for the loading process, but they are different.
Re:Announcing Rust 1.16 by eridius on Thursday March 16, 2017 @07:08PM (#13889968)
Hmm. I just ran `otool -hv /System/Library/Frameworks/Foundation.framework/Foundation` and it says the "filetype" header has the value "DYLIB". It looks like MH_BUNDLE is actually for plugin bundles, not for frameworks.
Re:Announcing Rust 1.16 by conradev on Thursday March 16, 2017 @08:15PM (#13890306)
Oh, I see! That makes sense. Preference bundles are type "BUNDLE" but frameworks are not. TIL.