The problem: create-frameworks.sh is limited to producing dynamic libraries. In use cases that make sense, static linking can lead to better optimization.
This adds a simple flag to create-frameworks.sh, -s, which overrides the mach-o format to instead be a static library. The resulting output frameworks, along with the final XCFramework, are produced as static libraries instead of dynamic libraries. Since the existing OpenSSL.framework is already just a simple repackaging of the libcrypto and libssl libraries, I don't believe that anything else needs to be touched.
The problem:
create-frameworks.sh
is limited to producing dynamic libraries. In use cases that make sense, static linking can lead to better optimization.This adds a simple flag to
create-frameworks.sh
,-s
, which overrides the mach-o format to instead be a static library. The resulting output frameworks, along with the final XCFramework, are produced as static libraries instead of dynamic libraries. Since the existingOpenSSL.framework
is already just a simple repackaging of thelibcrypto
andlibssl
libraries, I don't believe that anything else needs to be touched.Examples:
No worries if you'd prefer a different approach, or if this isn't in the scope of this project.