8

Since the iOS simulator is a simulator, why do I need to build specifically for it? Isn't the point of a simulator that it runs the real code in some sort of VM/sandbox?

So what are the actual differences in how building for device/simulator works, and how the resultant built apps differ?

Mr. Boy
  • 60,845
  • 93
  • 320
  • 589

3 Answers3

10

An application running natively on an iOS device is an ARM program. However, an application running in the iOS Simulator is an ordinary 32-bit (i386 architecture) Mac OS X program. In other words, the Simulator doesn’t simulate an iOS device down to the hardware level. It provides a faithful copy of the iOS environment, reimplemented to run natively on the Mac.

Vignesh
  • 10,205
  • 2
  • 35
  • 73
  • So it is literally compiled for a different architecture. In that case is it weird that some libraries I am using put the simulator/device binaries in the same location with the same names - so every time I build simulator I lose the device version, and vice versa? And how does an app which comes with pre-built dependency libraries (.a files) run on both the simulator and device? – Mr. Boy Apr 18 '12 at 09:09
  • @john You can use lipo tool which comes with xcode to make a fat (works for device and simulator )binary. – Vignesh Apr 18 '12 at 09:10
  • # make a new output folder mkdir -p ${PROJECT_DIR}/build/${BUILD_STYLE}-iphoneos/DTUtilities # combine lib files for various platforms into one lipo -create "${PROJECT_DIR}/build/${BUILD_STYLE}-iphoneos/libDTUtilities.a" "${PROJECT_DIR}/build/${BUILD_STYLE}-iphonesimulator/libDTUtilities.a" -output "${PROJECT_DIR}/build/${BUILD_STYLE}-iphoneos/DTUtilities/libDTUtilities-${BUILD_STYLE}.a" – Vignesh Apr 18 '12 at 09:12
6

The simulator build uses the i386 instruction set, since that is what your mac uses.

When you build for an iOS device, you are building either for the armv6 or armv7 instruction sets.

The point of the simulator is so that you can do some quick testing on your mac, without needing to use a device.

To learn more about instruction sets: http://en.wikipedia.org/wiki/Instruction_set

Rahul Iyer
  • 19,924
  • 21
  • 96
  • 190
  • Simulators never give memory warnings.But different devices have different memory ,so to create a good app we have to test it in both simulator and devices. check out for same question [link](http://stackoverflow.com/questions/380062/iphone-device-vs-iphone-simulator) – Pavan Apr 18 '12 at 08:59
5

The simulator and the device should run the same code just the same, nevertheless there are few issues that one should take it mind.

  1. The simulator can not run all functionality which the device can run, for example the simulator does not interact with a camera, GPS data is not present (but you can set a fixed location from the options) , and there are few other things along those lines.

  2. The simulator can be used to check your code and functionality much faster than dumping your code on the device while developing, nevertheless the simulator is using your computer's memory and CPU which means that it does not reflect the performances on a real device, speed and memory wise.

Good practice would be to test and develop mostly on the simulator, when your code and stable and working as planed - it is time to test it on the device itself for performances and other issues that are device specific.

I can elaborate more on the topic, but I this is a quick answer to your question.

chewy
  • 8,207
  • 6
  • 42
  • 70