StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Actually the problem is that MagTek provides you two separate .a files.</p> <p>If you look at the one in the Release-iphoneos and run the following command: </p> <pre><code>> lipo -info libMTSCRA.a Architectures in the fat file: libMTSCRA.a are: armv7 (cputype (12) cpusubtype (11)) </code></pre> <p>Likewise if you look at the one in Release-iphonesimulator...</p> <pre><code>> lipo -info libMTSCRA.a input file libMTSCRA.a is not a fat file Non-fat file: libMTSCRA.a is architecture: i386 </code></pre> <p>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. </p> <p>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: </p> <pre><code>libtool -static -o libMTSCRA_FAT.a Release-iphoneos/libMTSCRA.a Release-iphonesimulator/libMTSCRA.a </code></pre> <p>When you examine the output file, you should see:</p> <pre><code>>lipo -info libMTSCRA_FAT.a Architectures in the fat file: libMTSCRA.a are: armv7 (cputype (12) cpusubtype (11)) i386 </code></pre> <p>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.</p> <p>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 ).</p> <p>Et voilà !</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload