The purpose of universal binaries is to include in only one file the code of one module compiled for different architectures. Universal (or Fat): non-executable binary files that contain code for multiple architectures.MACH-O: binary files that contain code for a single architecture.In macOS, there are two categories of binary files: The bad news is that that's precisely what we need to do, the good one is that Xcode does the switching libraries work for us. Should we have two versions of the library, one for each architecture, and replace them every time we want to run on a different platform? Well, yes, and not.

If we repeat the process above specifying the arm64-apple-ios architecture we might be able to run the app on a real device, however, we won't be able to run it on the simulator.

However, if you try to run the app on a real device, you will still get an error. If you replace the old library file ( libmathvec.a) in Xcode with the newer one, you will see that the warning will disappear when running the app on the simulator. Gcc -c addvec.c multvec.c -target x86_64-apple-ios-simulator # Create object files again by specifying output architecture

We'll use the file mathvec.h as the header of the library, so we need to add the following function definitions to it:Įxport SDKROOT =/Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/iPhoneOS.sdk.

Delete the mathvec.c file you created in step 2.

At this point, Xcode will ask you whether you want to configure an Objective-C bridging file for the project.

Name it mathvec.c and check the option to include its corresponding header file mathvec.h.

Click on File > New > File… and choose a C file from the list.

Make sure you check the option Copy items if needed and also select the target in which the library should be included.

Drag the library to the project in Xcode.

To include the library into the project we need to execute the following steps: # To create a dynamic library we should use: # libtool -dynamic addvec.o multvec.o -o libmathvec.dylib Including the library in an Xcode project Libtool -static addvec.o multvec.o -o libmathvec.a # create a static library (libmathvec.a) from the object files # create the object files for each input files (addvec.o and multvec.o)

How to create a c++ project in xcode