#Mac os 7 emulator for windwos Pc
I'm sure there are other problems in this space, its not ideal (though its pretty cool)Īnyway, unless Microsoft have a compiler-toolset that can target both the Phone CPU and the regular Windows PC CPU, they are stuck with emulation at the CPU level, rather than at the Operating System Level. There are some APIs that Apple have let bleed into the wrong SDKs, I recall there were issues with NSTask being available in the SDK even though it wasn't on the iPhone itself, for example. The problems that Rob Napier mentions are probably related to using native headers and libraries in his build (call those AppKit). There is no notion of "emulating a CPU" which is presumably what the Windows Phone 7 Emulator is doing, something similiar to the MacOS Virtual PC product of years ago (that Microsoft bought from Connectix, as I recall)
#Mac os 7 emulator for windwos full
This means that your code runs at full "machine" speed in both environments. You link against special libraries that are for an ARM CPU, again which implement the UIKit. When you build for the device, you are compiling for an ARM CPU.
You link against special libraries that are for an x86 CPU but which implement the functions that are part of the iPhone operating system (call that UIKit) When you build for the simulator, you are compiling for an Intel x86 CPU. What you need to understand is that the iPhone Simulator is an OPERATING-SYSTEM simulator, not a DEVICE simulator.
Boy, there's a lot of "emulators are this, simulators are that" in some of those answers and I feel more confused after reading them, especially when we get into suggestions that things are "re-written for that computer"
0 kommentar(er)
