I know I've mentioned it before and you bring it up again: it's probably possible to create a single fat lib with ppc, i386, x86_64, and arm64. This is, however, at best an academic exercise.
Message: 1Date: Sun, 1 May 2022 10:52:17 +0200From: IOhannes m zm?lnig <zmoelnig@iem.at>To: pd-dev@lists.iem.atSubject: Re: [PD-dev] [PD] how to compile externals for apple silicon?Message-ID: <2a870fec-b81f-75d0-81e3-5a59462e2ebc@iem.at>Content-Type: text/plain; charset="utf-8"; Format="flowed"On 5/1/22 09:42, Dan Wilcox wroteYou cannot build for i386. Support for that arch was famously removed in macOS 10.15 and those versions of Xcode which use its SDK, probably version 10 or so. Modern fat libs arm64 and x86_64.
just to add a bit of confusion...technically, i think there's no difference between a "modern" and a "legacy" fat lib: it's a file format that can contain multiple architectures.there's absolutely nothing keeping you from having a fat binary that contains arm64, x86_64, i386 and ppc.the only obstacle is, that there is no compiler that can create binaries for all of these architectures.but you can create the binaries on multiple systems (different macOS/OSX versions; different Xcode installations) and then use 'lipo' to merge the different single-arch binaries into a single fat one.