From Apple’s website: Binary Compatibility and Frameworks While your app’s runtime compatibility is ensured, the Swift language itself will continue to evolve, and the binary interface will also change. To be safe, all components of your app should be built with the same version of Xcode and the Swift compiler to ensure that they work … Read more
They are called cross project references. From the link below: Cross-project references are a convenient way to create relationships between two separate Xcode projects. One method of creating shared frameworks is using sub-projects. You can also do it with single projects. More here: https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Tasks/CreatingFrameworks.html Other links: Xcode 4 Adding a Sub Project
In Xcode 4, in the left sidebar, select the project file at the top: 1) Make sure your target is selected in the main view, and you should see 5 tabs at the top, 2) Click the “Build Phases” tab, 3) Click the arrow to the left of the “Link Binary With Libraries” row, 4) … Read more
I’ve done with the following steps. Create a framework project, for example named “FooKit”. (Cocoa Touch Framework to be selected) Create a “.swift” file and add a public symbol, for example public func foo(), to it. Create an use-side (app) project. (I’ve chosen Single View Application) Open the root directory of “FooKit” by Finder, drag … Read more
The article claims it is using the “registry design pattern”; is that the universal name for this design in the industry? Yes, but the implementation could obviously differ. Basically, a registry is a container for shared objects. In the really basic version, you could use an array. As such, the variable $GLOBALS could be called … Read more
You can create a pod and publish it. Check https://guides.cocoapods.org/making/making-a-cocoapod.html Sample Podspec file with XCFramework + Third party dependency Pod::Spec.new do |s| s.name=”XCFrameworkTest” # Name for your pod s.version = ‘0.0.1’ s.summary = ‘Sample Spec’ s.homepage=”https://www.google.com” s.author = { ‘Sample’ => ‘[email protected]’ } s.license = { :type => “MIT”, :text => “MIT License” } s.platform … Read more
Important note: This answer was written before iOS 8 was announced. While the technical details still apply to system frameworks, it is now possible to build your own, dynamically linked frameworks that ship within your app bundle. There are restrictions, e.g., only an app and its extensions can link to the same instance of an … Read more
The AppPool’s .NET CLR Version is different from the .NET Framework Version. The .NET CLR Version 4.0 is the CLR base for the following .NET Framework Versions: 4 4.5 (including 4.5.1 and 4.5.2) 4.6 (including 4.6.1 and 4.6.2 Preview) So having a .NET CLR Version of 4.0 just means you support the above Frameworks, which … Read more
Nested frameworks are not supported on iOS (see technotes). The only legit solution at the moment is to link “embedded” frameworks directly to a hosting app. *XCFramework is mainly an aggregation of platform specific binaries and has nothing to do with embedding frameworks unfortunately.
I got a message from an Apple developer stating that they’ve observed this problem, and that it could be fixed by moving the .framework to a subfolder of the project. Apparently the module .. was built in directory error appears only if the .framework is in the same folder as the .xcodeproj aka $(PROJECT_DIR). However … Read more