Posts

Post marked as solved
6 Replies
19k Views
Like https://forums.developer.apple.com/message/389765#389765, I am trying to create an xcframework file for a few third party libraries I'm using. Following the instructions from https://appspector.com/blog/xcframeworks, I1. Create platform-specific framework files:# Archive for device xcodebuild archive -scheme TestFramework -destination="iOS" -archivePath /tmp/xcf/ios.xcarchive -derivedDataPath /tmp/iphoneos -sdk iphoneos SKIP_INSTALL=NO BUILD_LIBRARIES_FOR_DISTRIBUTION=YES # Archive for simulator xcodebuild archive -scheme TestFramework -destination="iOS Simulator" -archivePath /tmp/xcf/iossimulator.xcarchive -derivedDataPath /tmp/iphoneos -sdk iphonesimulator SKIP_INSTALL=NO BUILD_LIBRARIES_FOR_DISTRIBUTION=YESAt this point, I've gotten two frameworks with swiftmodule files; everything looks good. The frameworks do *not* come with swiftinterfacefiles, but I think that is alright as these are objc projects. Then, I2. Combine the individual frameworks to form a single xcframework file:# Build xcframework with two archives xcodebuild -create-xcframework -framework /tmp/xcf/ios.xcarchive/Products/Library/Frameworks/TestFramework.framework -framework /tmp/xcf/iossimulator.xcarchive/Products/Library/Frameworks/TestFramework.framework -output /tmp/xcf/TestFramework.xcframeworkHere, xcodebuild doesn't fail, but it emits a curious error:No 'swiftinterface' files found within '/Users/user/git/ReactiveObjC/output/xcf/ios.xcarchive/Products/Products/Library/TestFramework.framework/Modules/TestFramework.swiftmodule'.Crucially, the xcframework package does not contain the individual frameworks or folders specified in the Info.plist file. Obviously, when I try to link to the xcframework in this state, I get a bunch of "missing symbols" linker errors.Why is this? What must I do to get xcodebuild to create the xcframework completely?NB: Manually creating the folders seems to work for now, but this feels wrong and is brittle – Apple can change the way xcodebuild works anytime.
Posted
by pkoggg2.
Last updated
.
Post not yet marked as solved
5 Replies
2.1k Views
We have a macOS app built using a custom installer. Our installer containsthe main appa helper app that is embedded within the main appa postinstall script that launches the helper appOn a successful installation, the postinstall script launches the helper app, which depends on the TMPDIR environmental variable to function correctly. Unfortunately, the installation process takes place within the PackageKit sandbox, changing the value of TMPDIR. This causes our helper app to not work correctly when launched through the postinstall script. Is there a way to start my helper app on a successful installation without changing TMPDIR?
Posted
by pkoggg2.
Last updated
.