Building for iOS Simulator-x86_64 but attempting to link with file built for iOS Simulator-arm64 Please find the below environment details, xcode-select --print-path /Applications/Xcode-beta.app/Contents/Developer xcodebuild -version Xcode 12.0 Build version 12A8189h xcodebuild -showsdks iOS SDKs: iOS 14.0 -sdk iphoneos14.0 iOS Simulator SDKs: Simulator - iOS 14.0 -sdk iphonesimulator14.0 macOS SDKs: DriverKit 20.0 -sdk driverkit.macosx20.0 macOS 11.0 -sdk macosx11.0 tvOS SDKs: tvOS 14.0 -sdk appletvos14.0 tvOS Simulator SDKs: Simulator - tvOS 14.0 -sdk appletvsimulator14.0 watchOS SDKs: watchOS 7.0 -sdk watchos7.0 watchOS Simulator SDKs: Simulator - watchOS 7.0 -sdk watchsimulator7.0 system_profiler SPSoftwareDataType Software: System Software Overview: System Version: macOS 10.15.6 (19G73) Kernel Version: Darwin 19.6.0 Boot Volume: Macintosh HD Boo
Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for
167,373 results found
Post
Replies
Boosts
Views
Activity
Hi! My Python-Kivy app works on iOS now! Both on the Xcode iPhone 7 simulator AND on a physical iPhone 7. But when I deploy it on the physical iPhone 7 I get 85 annoying warnings of this form: ld: warning: building for iOS, but linking in .tbd file (filename.tbd) built for iOS Simulator What can I do about that? Thank you. Henrik
I am stuck with this linking error for days. I recently updated to Xcode12 and my project building and running fine for real devices. But when I try to run for Simulator I am getting this error. building for iOS Simulator, but linking in object file built for macOS, file '..customLib.a' for architecture x86_64 My customLib is a .a library built with Xcode12 too. lipo -info customLib.a Architectures in the fat file: customLib.a are: armv7 armv7s i386 x86_64 arm64 How to resolve this issue?
I want run a ios simultor demo, But meet this error . I have checked the archs of the framework file If I want run this on Apple Silicon Mac ,How to fix , In Apple Silicon , I meet same problem building for iOS Simulator, but linking in object file built for iOS, file '../SDK/***.framework/***' for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) How to fix it ? Hope someone can give a perfect answer Hope to get the answer of the deep principle
Aouch ... 6 years old ! Because XCFramework don't work with embedded statics lib, I use a workaround with two run scripts in build phase. Note : for both script, check Based on depedency analysis to skip if not necessary, be sure For install builds only is uncheck First script at the beginning of the build phase : if [ $ARCHS == 'arm64' ] then cp -rf ./lib/iphone/libName.framework ./lib/libName.framework else cp -rf ./lib/simulator/libName.framework ./lib/libName.framework fi Second script at the end of the build phase rm -rf ./lib/libName.framework ` Note : if your framework is still there when you change your arch (i.e. from simulator to device ) the phase prepare build will stop your build. That's the reason of the deletion at the end of the build phase, without the second script you will have this error : path.xcodeproj Building for iOS, but the linked and embedded framework
Hi everyone, I got an issue when running my project in Xcode 12 beta 4. But running perfect in Xcode 11. error message like below: /Users/a/Documents/iOS/Project/project.xcodeproj Building for iOS Simulator, but the linked library 'libssl-tvOS.a' was built for tvOS + tvOS Simulator. /Users/a/Documents/iOS/Project/project.xcodeproj Building for iOS Simulator, but the linked library 'libcrypto-tvOS.a' was built for tvOS + tvOS Simulator. I had google it, but I can't find the answer. Does anyone can help me to solve this problem? Thanks~
Hi guys, I have Xcode 15.2 + MacOS Sonoma 14.2.1 + iPhone SDK 17.2 + Apple M3 chip When I build my project with FMOD for Unreal 2.0.2.20 for iOS Simulator on have an error: /Plugins/FMODStudio/Binaries/IOS/libfmodL_iphoneos.a(libfmodL_iphoneos.a-arm64-master.o) building for iOS Simulator, but linking in object file built for iOS**, file '/Plugins/FMODStudio/Binaries/IOS/libfmodL_iphoneos.a' Found that in downloaded latest verison fmodstudio20220ue5.3mac.zip from https://www.fmod.com/download#fmodforunreal inside folder Plugins/FMODStudio/Binaries/IOS there are no files for iOS Simulator (so it's not builded for support it or they just forgot to do it) So next i found on page https://www.fmod.com/docs/2.02/api/platforms-ios.html#ios-specific-starter-guide that they Released iOS simulator binary for Core Engine and Studio Engine FMOD Core Engine librar
While trying to download dependencies via Carthage in our project with Xcode 12 beta 5 and 6 version. I am getting dylib linking error as below: ld: building for iOS Simulator, but linking in dylib built for iOS, file 'Carthage/Build/iOS//XXXFrameworkName.framework/XXXFrameworkName' for architecture arm64 It is working as expected in below Xcode 12 version(i.e Xcode 11.x). Could you please help on this? Is this a Xcode 12 beta version issue?
I'm using an open source library (libturbojpeg), and the library has been built more or less the same for years. The 2.0.2 version links fine for Device and Simulator in both Xcode 11.3 and 11.4.1-beta.But newer releases generate warnings in 11.3 when using 2.0.3 or newer (for example):ld: warning: building for iOS Simulator, but linking in object file (/Volumes/Data/git/PhotoScrollerSwiftPackage/Libraries/libturbojpeg.a(jdapimin.c.o)) built for macOSWorse yet, in Xcode 11.4.1-beta, those turn into hard errors and the build fails:error: Building for iOS Simulator, but the linked library '208libturbojpeg.a' was built for macOS + iOS. (in target 'LTJTest' from project 'LTJTest')This issue first showed up here (as best I can tell) in this thread.Since these really only affect the Simulator builds, is there anyway to disable them?
Here's the obvious method:- have app and custom framework projects in the same workspace- in the app main target, add the framework to General->Embedded Binaries (as expected, this also adds the framework to General->Linked Frameworks and Libraries, and to the two build phases 'Link Binary With Libraries' and 'Embed Frameworks'This worked fine in the simulator, then crashed on the device with:dyld: Library not loaded: @rpath/XX.framework/XX Referenced from: /var/containers/Bundle/Application/E551758E-ED3C-486E-B6AE-856B5872C14D/AA.app/AA Reason: no suitable image found. Did find: /private/var/containers/Bundle/Application/E551758E-ED3C-486E-B6AE-856B5872C14D/AA.app/Frameworks/XX.framework/XX: mach-o, but wrong architectureWith use of lipo etc and then squinting at the Xcode General tab (hard to read because the paths don't wrap, and the mouseover path display is erratic), it's easy to figure out w
@Developer Tools Engineer We got a new framework from the manufacturer. When I run lipo info on the 3 framework files I'm trying to build with I get: Architectures in the fat file: ...MTBeaconPlus.framework/MTBeaconPlus are: x86_64 arm64 Architectures in the fat file: ...iOSDFULibrary.framework/iOSDFULibrary are: x86_64 arm64 Architectures in the fat file: ...ZIPFoundation.framework/ZIPFoundation are: x86_64 arm64 I added arm64 and x86_64 to my architectures list in build settings. I want to build my framework now for Any iOS simulator device (arm64, x86_64) I'm getting an error saying: building for 'iOS-simulator', but linking in dylib (...MTBeaconPlus.framework/MTBeaconPlus) built for 'iOS' Why is this happening? It would make sense to me that you'd need framework files built for x86_64 and arm64 as lipo found when building for this option Any iOS
If it helps, here the full error: Building for 'iOS', but linking in dylib (/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/System/Library/Frameworks/MessageUI.framework/MessageUI.tbd) built for 'iOS-simulator'
In Xcode12 beta4, I encounter a failure in my project. I can run the Project on my device, but it is not running in the simulator. And when I use the beta3 or Xcode11, it won't happen. I get the failure message: ld: in /libwebrtc.a(dequantizemmx.o), building for iOS Simulator, but linking in object file built for free standing, file 'libwebrtc.a' for architecture x8664. Please help me what to do in Xcode 12.4. Do I have to change settings in Xcode 12.4.
(Offtop: Looking through other similar questions with zero to one answers, I don't believe in miraccle, that someone would answer me, but still think it worth trying)My setup is pretty simple (Swift 2.3 & Xcode 8B2):- Using Carthage I have build Other.framework- MyApp has embeded My.framework framework.- The app and framework projects are under one Xcode workspace.- I hade linked Other.framework to My.framework ONLY (that means, MyApp is not linked to Other.framework at all). The point here is that, MyApp does not need to use Other.framework API.Here is the problem: Everything seems to work fine, until I Build & Run the app on the device. The app launched and than the process is aborted with the following Xcode error:dyld: Library not loaded: @rpath/Other.framework/Other Referenced from: /private/var/containers/Bundle/Application/DCF0331F-FF23-43CF-AE79-B3857D5A6EE3/MyApp.app/Frameworks/My.framework/My Reason: no suitable image fo
I'm trying to embed a self-built copy of the WebKit frameworks to a macOS app. Most importantly I hope to get some features to work which Safari offers, but WKWebView in macOS doesn't (getDisplayMedia, Service Workers, WebInspector). Many years ago I was successful in using a self-built WebKit copy in this Mac app, but it seems the WebKit framework got more complex since them, I guess because of WKWebView's architecture. That time I had to open the projects for the main frameworks in Xcode, select the framework bundle in the target and change the Installation Directory setting to the path @executable_path/../Frameworks. After building WebKit using the build script, I could use otool -L to confirm the changed installation path, which then was displayed for example as @executable_path/../Frameworks/WebCore.framework/Versions/A/WebCore I tried the same with a current WebKit build: I copied the products for WebKit.f