I was trying to make a sample code run download by the link
http://www.magtek.com/support/software/downloads/sw/99510108.zip
This is a card reader api ,here is a sample code.When I run this code I got the error:
ld: warning: ignoring file /Users/gaurav.garg/Downloads/99510108/SampleCode/Lib/libMTSCRA.a, missing required architecture i386 in file
Undefined symbols for architecture i386:
"_OBJC_CLASS_$_MTSCRA", referenced from:
objc-class-ref in MagTekDemoAppDelegate.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The class MTSCRA is only a header file,And the solution that I have cheked That we have to add the .m file in compiled source path of build build phase of target...but unfortunately I don't have the MTSCRA.m file.MTscra.h have the AudioToolBox and externalAccesory framework.
Actually the problem is that MagTek provides you two separate .a files.
If you look at the one in the Release-iphoneos and run the following command:
> lipo -info libMTSCRA.a
Architectures in the fat file: libMTSCRA.a are: armv7 (cputype (12) cpusubtype (11))
Likewise if you look at the one in Release-iphonesimulator...
> lipo -info libMTSCRA.a
input file libMTSCRA.a is not a fat file
Non-fat file: libMTSCRA.a is architecture: i386
So the real answer is to create a new libMTSCRA.a for DEBUG that is n-way FAT by combining the two using lib tool and then creating separate DEBUG and RELEASE library search paths.
To start you would go to the directory above where MagTek keeps the two different versions of libMTSCRA.a When you are there, you will run the following command:
libtool -static -o libMTSCRA_FAT.a Release-iphoneos/libMTSCRA.a Release-iphonesimulator/libMTSCRA.a
When you examine the output file, you should see:
>lipo -info libMTSCRA_FAT.a
Architectures in the fat file: libMTSCRA.a are: armv7 (cputype (12) cpusubtype (11)) i386
Then in your project, create two folders (aka groups) "debug" & "release" and then restructure the DEBUG and RELEASE Library Search Paths to use these respective directories.
Lastly, rename libMTSCRA_FAT.a to libMTSCRA.a and place it in the debug search path keeping the iOS (armv7 (cputype (12) cpusubtype (11))) in release. The reason we do this is because while it might be ok to use this newly created .a file in debug mode it is considered bad taste to push this into production because we have no way to confirm that the merged lib is 100% what we intended ( the merge of the archs ).
Et voilà !
Undefined symbols for architecture i386:
It means that the library you are linking against does not have symbols for i386. Which means you can not use the simulator. You will need to run the sample on the device or get the version of the library created for the simulator.
You need to make sure you are including all of the Frameworks that are required by that library.
Related
I'm quite new to Xcode and Iphone development and ran into the following problem:
I opened a new project and added *.h and a *.a files (which I recived from a certain device vendor).
I get the following warning:
ld: warning: ignoring file /Users/udi/Desktop/Xcode/Xcode Projects/Scosche/libmyTrekSDK_armv7.a, missing required architecture i386 in file /Users/udi/Desktop/Xcode/Xcode Projects/Scosche/libmyTrekSDK_armv7.a (2 slices)
If I ignore the warning, and try to instanciate the class that is given to me in the header file, I get these errors:
ld: warning: ignoring file [Path/FileName.a], missing required architecture i386 in file [Path/FileName.a] (2 slices)
Undefined symbols for architecture i386:
"_OBJC_CLASS_$_HRMonitor", referenced from:
objc-class-ref in ViewController.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
I've checked the Framework Search Pathes (as mantioned in many other posts) and it clear.
More info:
I'm Using Xcode 4.6.1
The files are currently located at project's root folder.
I'm using a Single View Application tamplate.
Appreciate any help
This warning means that you're trying to use library made for Device (ARM) with your Simulator (i386).
You can use this terminal command to create a universal library:
lipo -create lib_arm.a lib_i386.a -output lib_universal.a
More info about lipo command here.
Change your target's "Build Settings > Build Active Architectures Only" to "No"
This is doing the same thing as Dmitry Zhukov's answer but doing it thru Xcode instead of going around its back.
If you are working with a 3rd party code, keep in mind that some SDKs may not work on the simulator. The same build error I have encountered vanished, when I ran the project on the device.
I'm creating a static library with some class files, and the library is creating well but if I install to library to another new Xcode project it showing error and the error is as follows ,
ld: warning: ignoring file /Users/rajesh/Desktop/Quntiles/01-03-2013/ConnectionExample-1/libAVTEmployee.a, file was built for archive which is not the architecture being linked (armv7s): /Users/rajesh/Desktop/Quntiles/01-03-2013/ConnectionExample-1/libAVTEmployee.a
Undefined symbols for architecture armv7s:
"_OBJC_CLASS_$_AVTEmployee", referenced from:
objc-class-ref in XMLParser-E51A1142A3EEED70.o
ld: symbol(s) not found for architecture armv7s
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Can any one please help me, how can I fix this issue so that I can use the my static library in my new project ,
I'm using Xcode 4.6 version.
Thanks in advance.
Probably your static library was created or compiled using an older version of XCode that didn't support armv7s architecture. Open the static library project and make sure that Architectures contains armv7 and armv7s architectures and Build Active Architectures Only is set to No under Build Settings.
According to the literature, an A6 processor will execute ARMv7 code. My project is failing at link because a library was built for ARMv7, but the application is built for ARMv7s.
A typical message is (when I attach my iPad 4 (Retina) or iPhone 5):
ld: warning: ignoring file /usr/local/ssl/iphoneos/lib//fipscanister.o, file was built for armv7 which is not the architecture being linked (armv7s): /usr/local/ssl/iphoneos/lib//fipscanister.o
ld: warning: ignoring file /usr/local/ssl/iphoneos/lib//libcrypto.a, file was built for archive which is not the architecture being linked (armv7s): /usr/local/ssl/iphoneos/lib//libcrypto.a
Undefined symbols for architecture armv7s:
"_FIPS_incore_fingerprint", referenced from:
_FINGERPRINT_premain in fips_premain.o
"_FIPS_signature", referenced from:
_FINGERPRINT_premain in fips_premain.o
"_FIPS_text_start", referenced from:
_FINGERPRINT_premain in fips_premain.o
ld: symbol(s) not found for architecture armv7s
I know I can resolve this by removing ARMv7s from Valid Architectures (VALID_ARCHS), but I'm not sure why since the A6 processor can execute A5 object code. Or I can perform an additional build of the library for the ARMv7s architecture, but that's more work and requires a different on-disk directory structure.
Is there any magic to link an ARMv7 library with an ARMv7s application?
From Jim Grosbach on the Xcode mailing list, the linker switch -allow_sub_type_mismatches should allow ld to proceed with linking. And from Apple's ld man pages:
-allow_sub_type_mismatches
Normally the linker considers different cpu-subtype for ARM
(e.g. armv4t and armv6) to be different different architec-
tures that cannot be mixed at build time. This option
relaxes that requirement, allowing you to mix object files
compiled for different ARM subtypes.
There's also a Changelog entry that details the environmental variable called LD_ALLOW_CPU_SUBTYPE_MISMATCHES.
However, I found -allow_sub_type_mismatches simply did not work on Xcode 4.5.2. Grepping the web reveals a few Apple RADAR's for -allow_sub_type_mismatches. See, for example, radar://6134468.
Hopefully its fixed by now, but nothing surprises me when it comes to Apple and their defective software.
I want to use iphone-exif library for EXIF data in my proj. But i dont know if i done any mistake or not it gives error like
Undefined symbols for architecture i386:
"_OBJC_CLASS_$_EXFJpeg", referenced from:
objc-class-ref in ViewController.o
ld: symbol(s) not found for architecture i386
please give some solution for that.
Thanks in advance for ur answers.
Instead of using that library Please go through this Solution
Actually I had the same problem so I had created it for myself for getting EXIF info purpose..
When you download iPhone-exif your will find two precompiles libraries.
Release-iphoneos/libiphone-exif.a
Release-simulator-iphonesimulator/libiphone-exif.a
Depending on where you'd like to run your app, you need to link against the right file.
You probably added Release-iphoneos/libiphone-exif.a to your project and then you tried to run in on the Simulator (i386 architecture!).
Easiest way:
Create a universal library of the both above.
Open terminal
Cd to your iphone-ex download folder (cd iphone-exif-0-9)
lipo -arch i386 Release-simulator-iphonesimulator/libiphone-exif.a -arch armv6 Release-iphoneos/libiphone-exif.a -create -output libiphone-exif-universal.a
add the file "libiphone-exif-universal.a" to your Xcode project
But i've just found out that there is a armv7 build missing. If you'd like to place your app on the appstore you once need also to build the library also for armv7 (out of the sources!)
i get this error when i am trying to use my compiled static library in my iphone aplication. I have no frigging idea what's wrong.
ld: warning: ignoring file /Users/rw/Library/Developer/Xcode/DerivedData/MSTicketingSaaS-gkznscznevvifjesoapzgwycbces/Build/Products/Debug-iphoneos/libMylib.a, file was built for archive which is not the architecture being linked (armv6)
Undefined symbols for architecture armv6:
"_OBJC_CLASS_$_AppData", referenced from:
It worked before upgrading to Xcode 4.0.2
I added the i386 architecture and now it compiles for the simulator but NOT for the device.
Check with lipo which is the architecture your lib has been built for:
lipo -info <path_to_lib>
If it does not contain "arm6" then you should go back to the library project and build it for the proper architecture. If this does not help, please, give more detail about the structure of your project(s).