Building Adobe AIR Applications
Building Adobe AIR Applications
Building Adobe AIR Applications
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
BUILDING ADOBE <strong>AIR</strong> APPLICATIONS<br />
Developing <strong>AIR</strong> applications for the desktop<br />
Creating a native installer for an application that uses native extensions<br />
You can build a native installer out of the source files for the application and the native extension packages that the<br />
application requires. Use the -package command with the following syntax (on a single command line):<br />
adt -package <strong>AIR</strong>_SIGNING_OPTIONS<br />
-migrate MIGRATION_SIGNING_OPTIONS<br />
-target native<br />
[WINDOWS_INSTALLER_SIGNING_OPTIONS]<br />
installer_file<br />
app_xml<br />
-extdir extension-directory<br />
[file_or_dir | -C dir file_or_dir | -e file dir ...] ...<br />
This syntax is the same syntax used for packaging an a native installer, with two additional options. Use the -extdir<br />
extension-directory option to specify the directory that contains the ANE files (native extensions) that the<br />
application uses. Use the optional -migrate flag and MIGRATION_SIGNING_OPTIONS parameters to sign an update to<br />
an application with a migration signature, when the primary code-signing certificate is different certificate than the<br />
one used by the previous version. For more information see “Signing an updated version of an <strong>AIR</strong> application” on<br />
page 188.<br />
For details on ADT options, see “<strong>AIR</strong> Developer Tool (ADT)” on page 156.<br />
The following example creates a DMG file (a native installer file for Mac OS) for an application that uses native<br />
extensions:<br />
adt -package<br />
-storetype pkcs12<br />
-keystore myCert.pfx<br />
-target native<br />
myApp.dmg<br />
application.xml<br />
-extdir extensionsDir<br />
index.html resources<br />
Creating a native installer from an <strong>AIR</strong> file or an <strong>AIR</strong>I file<br />
You can use ADT to generate a native installer file based on an <strong>AIR</strong> file or an <strong>AIR</strong>I file. To build a native installer based<br />
on an <strong>AIR</strong> file, use the ADT -package command with the following syntax (on a single command line):<br />
adt -package<br />
-target native<br />
[WINDOWS_INSTALLER_SIGNING_OPTIONS]<br />
installer_file<br />
air_file<br />
This syntax is similar to the syntax for creating a native installer based on the source files for the <strong>AIR</strong> application.<br />
However, there are a few differences:<br />
As the source, you specify an <strong>AIR</strong> file, rather than an application descriptor file and other source files for the <strong>AIR</strong><br />
application.<br />
Do not specify signing options for the <strong>AIR</strong> file, as it is already signed<br />
To build a native installer based on an <strong>AIR</strong>I file, use the ADT -package command with the following syntax (on a<br />
single command line):<br />
Last updated 7/8/2013<br />
56
Change language