This is the title article for a series of posts that take a look into the components you’ll need, in order to make a native extension for four different platforms.
In a nutshell, you need three components for an AIR Native extension. Two of them are made by you and the third one is provided by Adobe.
You need to provide (write) two libraries:
- an AIR library, compiled as a .swf file;
- a native library, compiled either as an .a, .jar , or .DLL file.
Adobe has provided the ‘glue’ for these two in the form of a native API that sits between your two libraries and translates ActionScript calls and data to native code and vice versa. It comes in two flavours:
- AIR C API;
- AIR Java API.
Which one is your platform?
The following posts let you zoom in and see what library format you will need for each platform: