iOS simulator debug ane

Source: Http://www.tuicool.com/articles/AFRJzi

Use the iOS emulator to detect and debug air applications supplemental Articles

Air3.4 's here.
The application can be deployed directly to the simulator and deployed to the real machine.

Air3.3 when very bitter force, you can only go to the simulator inside the application can not be removed, to the Air3.4 after not only to install, but also can be deleted, this shows that the direct use of Xcode iOS Simulator air program to debug the era of formal arrival.

Author Huang Jinwei

In fact, this article is a supplement to this article:

Http://www.adobe.com/cn/devnet/air/articles/ios-simulator.html

Requirements Essential Knowledge

1. You know how to develop mobile applications with air and install it in your program
2. You know how to pack ane and call it in the program.
3. You know how to run your program on the Xcode emulator.

User Level
Intermediate

Required Products

• Adobe AIR

Here's how to generate a. A file for use with simulators actually, the process of debugging the ANE program is similar to the one above, except that you need to produce an ane file that can be used by the x86 architecture. Here are three steps to do:

1. Generate the. A file for the iOS simulator.
2. Add the Iphone-x86 node.
3. Target adds Iphone-x86.

A lot of people are probably stuck in the first step, as a Xcode rookie user, how do you know if your generated. A file is ARM architecture or x86 architecture? How do I configure it?

Xcode first look at your library settings is not like this:

If so, we go to a very boring but very useful build script.

I use rakefile here, no make is because I can't write makefile.

But these things all pass.

First, the description of the predecessor variable:

#project Path Configuration#ADT Path$SDK _bin ="~/dropbox/air3.3/bin"#Project Target $ane _project_name =  "apppurchase"  # Project native Lib location  $native _ios_path =  "Native/nativelib"  #Project as Lib location  $native _as_path =  "Native/aslib " #native project location  $native _ios_project_path =  "#{ $native _ios_path}/#{< span class= "variable" > $ane _project_name}.xcodeproj " #sdk version  $ios _SDK =  "5.1"  #project buildtype:release/debug $ Build_type =  "Debug"           

Here we use the command line integration processes the corresponding platform library:

#build. A file for native device   #{$native _ios_project_path}-target #{$ane _project_name}-configuration #{$ Build_type}-sdk "iphoneos#{$ios _sdk}" '   #build. A file for simulator   #{$native _ios_project_path}- Target #{$ane _project_name}-configuration #{$build _type}-sdk "iphonesimulator#{$ios _sdk}"  

The corresponding console command is

"iphoneossimulator5.1"

How do you know about this SDK?

You can enter it in the console xcodebuild –sdk –version .

The. a file for the corresponding platform is then generated.

And then everything goes according to the top article.