— boreal-kiss.net

How to create universal static libraries on Xcode 4: the traditional way

[Note on 09.04.2011: This article will not be helpful unless you really need universal static libraries for distribution purposes etc. Instead, using workspace is a better way for daily development.]


Creating static libraries universal for iPhone device and simulator is a little bit tricky. On Xcode 3.x, the major way takes something like the following steps:

  • Create a build for the device (the armv6 and armv7 architecture).
  • Create a build for the simulator (the i386 architecture).
  • Merge the above builds to create a universal build using lipo.

Since Xcode, 4 a new command called archiving (Product > Archive) is introduced as a way to distribute applications and/or static libraries. At glance this is suitable to creating a universal libraries but is not. One can not select this option for the simulator environment (you will notice it is always grayed out). As such we still have to rely on the traditional way to create universal libraries (1).

In this article I will show you how to create such a fat static library on Xcode 4. Because the place for product builds of each project are completely changed from those of Xcode 3.x, we have to make a slight effort tailoring it to the Xcode 4.

How to do

In the following example I will use my project called BKMovableVC. On your workspace you can use whatever name you want, of course.

Step 1

Create a new Cocoa Touch Static Library target (File > New > New Target > Framework & Library) for the simulator environment. Naming is arbitrary as long as you can recognize (I named here BKMovableVC-iphonesimulator). Add related source files to the Compile Source pane and headers to Copy Header pane. For headers you can choose three possible places to put in, Public , Private, and Project (default is Project). For example if you choose Public, all headers will be automatically copied to the build directory, which is easy for me to continue following works.

[Note on 04.05.2011: There is a bug on Xcode 4; when all panes (Public, Private, and Project) in the Copy Header pane are closed or never opened before, pushing the add button causes a crash. Open one of them before adding files.]

From the Edit Scheme pane (Product > Edit Scheme), change its build configuration to Release. This enables you to create a Release build product once the build operation is done. This build operation supposes to be done on the simulator architecture (i386).

Step 2

Create a new static library target for the iPhone device environment. Naming is arbitrary but must be different from that of the simulator (I named here BKMovableVC-iphoneos). Add related source files and headers and change its build configuration to Release. Every step is just the same as that of the simulator except for the build architecture; this build operation supposes to be done on the device architecture (armv6 and armv7).

Now we have two targets, one for the device and the other for the simulator. When you build a product, the product will be placed under the following directory:


This place is shared by build products of all projects created on Xcode 4, which is quite different from the legacy place found on Xcode 3.x (each project has its own build directory). For example, if the name of the project is BKMovableVC, the Release build product for the simulator will be placed at


and that for the device will be found at


where BKMovableVC-xxxxxxx is a unique directory name automatically assigned by Xcode 4.

Step 3

Let’s merge them using the lipo command. Create a new Aggregate target (File > New > New Target > Other). I named it here BKMovableVC-ios4.3-0.9. On the Build Pheses pane select Add Run Script from the Add Build Phase button on the bottom-left corner.

Now we are about to run some scripts on the Run Script pane but here is a problem. How do we direct lipo to work with builds that are placed under the directory whose name is automatically assigned by Xcode 4 (e.g., BKMovableVC-xxxxxxx for the above case)? Fortunately it is easily solved by the Xcode 4 environment variable called ${BUILT_PRODUCTS_DIR}. This variable represents the path to the directory for a current build product. For example, when we create a Release build product for the simulator explained above, ${BUILT_PRODUCTS_DIR} corresponds to the following path:


Let’s continue. Write the following script on the Run Script pane. This lets lipo create a merged build product called libBKMovableVC-ios4.3-0.9.a (you can give it whatever name you want). If there is already the product with the same name lipo deletes it before the merge operation as shown in the first line.

rm -rf ${BUILT_PRODUCTS_DIR}/libBKMovableVC-ios4.3-0.9.a
lipo -create "${BUILT_PRODUCTS_DIR}/../${BUILD_STYLE}-iphonesimulator/libBKMovableVC-iphonesimulator.a" \
"${BUILT_PRODUCTS_DIR}/libBKMovableVC-iphoneos.a" -output \

Here is one trick. In this script the path representation to previously created build products such as libBKMovableVC-iphonesimulator.a looks odd because of “/../”. This is because the environment variable ${BUILT_PRODUCTS_DIR} depends on a current build phase (iPhone device, simulator, Debug, Release). For example, if this script runs for the Release build of iPhone device, the variable ${BUILT_PRODUCTS_DIR} will represent


However the build product for the simulator, libBKMovableVC-iphonesimulator.a, is not placed under this path, because it was created through a different build phase.


Let’s do all the flows in order. Do the following:

  1. Build the target BKMovableVC-iphonesimulator on the simulator. The build phase must be Release.
  2. Build the target BKMovableVC-iphoneos on the device. The build phase must be Release.
  3. Build the target BKMovableVC-ios4.3-0.9. on the device. The build phase must be Release.

Then you will have a static library universal for the device and simulator in the following directory:


You will also have header files depending upon your configuration (see the text above).


  1. Of course there could be a way to create a universal library on one scheme by tuning build settings but I have not found it by myself nor on the web. []
  1. Ambrose says: April 16, 20115:08 am

    Great post! Clear, precise and most of all, it works! Thanks for saving my time. Keep up the good work!

  2. Delta5 says: May 3, 20118:26 pm

    This tutorial looks great….. but xCode 4 crashes every time I try to add to the the ‘Copy Headers’ portion of the build Phases. What version of xCode were you using? I am using Version: 4.0 (4A304a).

    • borealkiss says: May 4, 20111:48 am

      Delta5, it’s an actual bug for Xcode 4 I have already experienced. When all panes (Public, Private, Project) in Copy Headers are closed (it’s never opened before), Xcode 4 crashes. Open one of them before adding files. Then push the add button.

  3. Andy says: May 4, 20111:24 pm

    This is great and thank you so much! Question -> the library that I produce needs to then be included in another project. In Xcode 3.2, I just included the library that was generated straight away in my other project and, as long as the “library project” was built first, the other project would automatically link in the newest version of the library. Is there any way in Xcode 4 such that, after building the library, I can just open my other project that depends on the built library and have it build? Or, do I need to manually (or, write a script; still manually since you need to run the script) move the newly generated .a file into my other project each and every time I re-generate the .a file?

    • borealkiss says: May 5, 20112:15 am

      Andy, use workspace that automatically build necessary libraries among projects. In the case in my blog post, you have to something manually, i.e., update libraries in one project first, then use it in another.

  4. Devang says: May 19, 20113:45 am

    Nice Article. I am able to get the products built as described, but am not getting the headers in the Release-iphoneos folder. Any suggestions/ideas on where i should get back and double check the things.

    • borealkiss says: May 19, 20114:00 am

      Devang, make sure you put headers into the Copy Headers pane (Public) in your device target. The detail how to copy headers is described in Step 1.

  5. Jamie Chapman says: May 27, 20113:38 am

    Fantastic post, thanks so much! Really helped me with my static library woes in Xcode 4.

  6. Erde says: July 3, 20116:12 am

    Nice post, but i’m having some trouble. I did everything as you stated it, no how should i do to get the .a file. I went to: /Library/Developer/Xcode/DerivedData/MyProject/
    Build/Products/Release-iphoneos but i didn’t find any .a file. What should i do to generate this file, should i only run the project? Could the file be in another directory? Thanks.

    • borealkiss says: July 3, 20116:26 am

      Erde, make sure you are running a static library target which includes some source files to be archived. Once again try only Step 1 and run the static library target in order to confirm you are actually creating a .a file.

      • Erde says: July 3, 20117:50 am

        what do you mean by ‘run the static library target’ ? Run the project on the device? i did step one again with no success after running the project.

        • Erde says: July 3, 20117:54 am

          the only thing i find in the directory is 2 files one with my project’s name and the other one MyProjectName.app.dSYM. Thanks for your time. By the way i’m doing Step 2 because i’m running on a device.

        • borealkiss says: July 3, 20118:04 am

          Set the proper scheme corresponding to your static library target and build it. It seems you only built the project scheme for your app.

          • Erde says: July 3, 20118:16 am

            you were absolutely right i was changing the scheme to the hole project and not to the static library i just created. Thanks, you saved my day!

  7. […] Do i have to do something special to generate this file. I’m following the steps in this […]

  8. ankit says: July 5, 20117:00 am

    How do i use this Library in my other project.. sorry for the lame question 😛

    • borealkiss says: July 5, 20117:18 am

      Just add the static library on your project with header files and necessary resources.

  9. slushduck says: July 11, 20115:50 pm

    Thanks very much! This was the best resource I’ve found and was able to create the static lib with little difficulty!
    Quick question though: once I’ve got the includes and the .a file, how does one go about packing it up into a nice Framework file?

    Thanks again!

    • slushduck says: July 11, 20116:18 pm

      Alright seems like a framework file is just a directory structure with no extra magic required. Simply organizing the files as below did the trick:

      MyLib.framework [add the .framework extension]
      -Headers [Add this directory]
      [put headers here]
      MyLib. [copy the static lib here and remove the .a extension]


      • sambit says: December 14, 20112:03 am

        Ok you have converted the .a file to .framework extension. Can you please tell me step by step procedure to do this. I have successfully got the libMyframe.a file. In the framework I have also added few images also. Now my problem is I have to convert this .a extension to . framework extension and add this to my project and even I need to distribute this framework. Please tell me mouse click by click step to do the conversion work till adding it to my project successfully.

        • borealkiss says: December 22, 20116:04 am

          Creating static libraries is the goal. Using frameworks is not allowed on iOS. You can do it only on Mac platform.

  10. kra says: July 24, 20111:51 pm

    That used to work fine in xcode 4.0 but now just boke with 4.1.
    When building for the simulator, xcode skips the device part and you can’t create the fat library.
    Weird part is that when you build for the device, it works fine… I’m trying to tweak the build settings to get that working again, but i’ve had no luck so far

  11. kra says: July 24, 20112:54 pm

    Ok, so I’m not quite sure I understand what has changed in XCode4.1, but it just won’t build as is.

    Basically, when building for device (iOS device selected in the scheme drop down), everything goes fine, Xcode is running properly both targets (device and sim).
    When building for simulator, Xcode is skipping the device target. Looks like the only defined arch is i386, the best thing I could get is have the device build… for i386. Not very helpful.

    The way I fixed our project for now is to do the following:
    – keep both device/sim targets as is
    – update the aggregate target to NOT depend on the device target
    – update the post build script to explicitly build the device target, so that would be something like:

    xcodebuild -configuration “${CONFIGURATION}” -target “Native Target Name” -sdk “iphoneos” ${ACTION} RUN_CLANG_STATIC_ANALYZER=NO BUILD_DIR=”${BUILD_DIR}” BUILD_ROOT=”${BUILD_ROOT}”

    It definitely lacks the elegance of your current solutions, but it works.

    I’d be very glad if anybody has any idea how to fix these issues…

  12. kra says: July 24, 20112:56 pm

    Oh, and one last thing.
    ${BUILD_STYLE} was deprecated a long time ago for ${CONFIGURATION}.
    Looks like apple decided to drop it altogether, so your lipo command line should be update with the new variable name.

  13. Jimmy Koerting says: July 28, 201111:20 am

    First of all – thanks for your nice howto here.
    I did like you showed it here and the creation of the lib worked like charme. But when I try to use it, the using project fails with ‘Symbol(s) not found for architecture armv7’ (and armv6 or i386 if I build with simulator):

    Undefined symbols for architecture armv7:
    “_myfuncition”, referenced from:
    -[useLibraryTestViewController buttonClicked:] in useLibraryTestViewController.o

    I did tried this NOT with objective-c code, but with c++ code. I’m new to both c++ and xcode but I want to include a given c++ library into a objective-c project for the iphone.

    Can you give me a hint why this happens? mylib.a is listed it the ‘Link Binary With Libraries’ pane and the header file is there too, so I have no clue what’s wrong.

    Any hint is really welcome!!


    • borealkiss says: July 28, 20114:58 pm

      It seems your library was not compiled for armv7. Searching the error messages on google will give you more info.

  14. Jimmy Koerting says: July 29, 20118:27 am

    That is the fun – it is. One build is done for armv6+armv7 and the other is for i386. This is why I’m confused. Could there be something from with my c++ code that raises such error. E.g. that my c++ file is not exposing the function, and this gives this misleading message? On the other hand, the compiler does not complain anything in my code, but right code does not say right code for THIS work, correct?

    Again, any further idea would be of help.


  15. Oscar Salvador says: December 5, 20117:15 pm

    Hi!. I found this tutorial and after reading the comments I was really excited. However i got stock when I tried to change the scheme and then I would get tons of errors and could not build. If I change the scheme again no errors. What am i doing wrong?

  16. Oscar Salvador says: December 5, 20117:17 pm

    this is for step 1

  17. Yogan says: December 9, 20119:49 am

    Great post!!!!! All works.

  18. sambit says: December 14, 20111:47 am

    I was successful till getting the .a file in the derived data folder.I also included the lib…. .a file to the link binary with libraries.But next when I compiled I got an error of i386.Can somebody tell me what to do. Have I added the framework properly or something more has to be done

  19. sambit says: December 14, 20111:53 am

    After creating the lib…. .a file next is how to convert it into .framework extension .

  20. morwen_eledhwen says: May 2, 20124:29 am

    great post, thanks so much! worked fine for me!

  21. Martouille says: June 11, 20125:16 am

    Just… awesome !

  22. Kiran Kumar says: June 20, 20122:07 am


    It is really very nice article for making your code secure creating static library!

    I have following your instruction and i created two+++ projects for iPhonesimulator and iphoneDevice.
    in this two project static library i add my customized classes where i can use in any other applications. for Device i do getting .a file but for simulator i am not getting any .a file. I don’t know wether my approach is incorrect. or i need to create in single project!

  23. Swathi says: July 10, 201212:56 am

    The merged static library is working for simulator but not for device. Am i doing any mistake here? The error I am getting is Undefined symbols for architecture armv7:
    “_OBJC_CLASS_$_TestingLibrary”, referenced from:
    objc-class-ref in AppDelegate.o
    ld: symbol(s) not found for architecture armv7
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    Please help me in this aspect

    • Swathi says: July 10, 20128:26 am

      I solved my problem. Great article 🙂 Thanks much

  24. Kevin says: January 29, 20138:22 pm

    I found this to be a good reference,

    Same basic idea but a much more complicated build script that will build a fat library in one (user initiated) step. It also is a good reference for other techniques that (in the authors opinion) don’t work as well. This post got me on the right track for building static libraries, but once I needed to manage more than one (with interdependencies) I had to find a simpler approach. So far this has worked very well for both internal use and distribution.

  25. Creating a library in C using Xcode 4.6 says: February 3, 20138:02 am

    […] 446 A library is a collection of functions, so Step 1 is to learn enough C to write one or more functions. Step 2, read an article about creating libraries on Xcode. This one appears to be good: How to create universal static libraries on Xcode 4: the traditional way | boreal-kiss.net […]

  26. Dylan Kenneally says: August 6, 201312:19 am

    Thanks for the article, the step by step approach detailed, and the things to look out for in XCode helped me get my binary built in a breeze.

Submit comment