![Download Download](/uploads/1/3/4/1/134121107/267383115.png)
To create a captive runtime bundle for Mac OS X, you must package the application while running under the Macintosh operating system. Package the application using the ADT bundle target: adt -package -keystore./cert.p12 -storetype pkcs12 -target bundle myApp.app myApp-app.xml myApp.swf icons resources.
Android offers a custom plugin for the Eclipse IDE, called AndroidDevelopment Tools (ADT). This plugin provides a powerful, integratedenvironment in which to develop Android apps. It extends the capabilitiesof Eclipse to let you quickly set up new Android projects, build an appUI, debug your app, and export signed (or unsigned) app packages (APKs) for distribution.
Android Development Tools (ADT) is a plugin for the Eclipse IDE that is designed to give you a powerful, integrated environment in which to build Android applications. ADT extends the capabilities of Eclipse to let you quickly set up new Android projects, create an application UI, add packages based on the Android Framework API, debug your applications using the Android SDK tools, and even. The new ADT Control app delivers on ADT’s commitment to provide new and innovative ways to help protect what matters most. More than a smart app, ADT Control app is the new interactive service that seamlessly connects the key devices in customers’ homes on one platform—so they work together and work smarter. To create a captive runtime bundle for Mac OS X, you must package the application while running under the Macintosh operating system. Package the application using the ADT bundle target. Adt -package -keystore./cert.p12 -storetype pkcs12 -target bundle myApp.app myApp.
If you need to install Eclipse, you can download it from eclipse.org/mobile.
Note: If you prefer to work in a different IDE, you do not need toinstall Eclipse or ADT. Instead, you can directly use the SDK tools to build anddebug your application.
Download the ADT Plugin
- Start Eclipse, then select Help > Install NewSoftware.
- Click Add, in the top-right corner.
- In the Add Repository dialog that appears, enter 'ADT Plugin' for the Name and thefollowing URL for the Location:
- Click OK. If you have trouble acquiring the plugin, try using 'http' in the Location URL,instead of 'https' (https is preferred for security reasons).
- In the Available Software dialog, select the checkbox next to Developer Tools and clickNext.
- In the next window, you'll see a list of the tools to be downloaded. ClickNext.
- Read and accept the license agreements, then click Finish. If you get a security warning saying that the authenticity or validity ofthe software can't be established, click OK.
- When the installation completes, restart Eclipse.
Configure the ADT Plugin
Once Eclipse restarts, you must specify the location of your Android SDK directory:
- In the 'Welcome to Android Development' window that appears, select Useexisting SDKs.
- Browse and select the location of the Android SDK directory you recentlydownloaded and unpacked.
- Click Next.
Download Sdk Adt Bundle
Your Eclipse IDE is now set up to develop Android apps, but you need to addthe latest SDK platform tools and an Android platform to your environment.To get these packages for your SDK, continue toAdding Platforms and Packages.
Troubleshooting Installation
If you are having trouble downloading the ADT plugin after following thesteps above, here are some suggestions:
- If Eclipse can not find the remote update site containing the ADT plugin,try changing the remote site URL to use http, rather than https. That is, setthe Location for the remote site to:
- If you are behind a firewall (such as a corporate firewall), make sure thatyou have properly configured your proxy settings in Eclipse. In Eclipse,you can configure proxy information from the main Eclipse menu inWindow (on Mac OS X, Eclipse) >Preferences > General > NetworkConnections.
If you are still unable to use Eclipse to download the ADT plugin as aremote update site, you can download the ADT zip file to your local machine andmanually install it:
- Download the ADT Plugin zip file (do not unpack it):
Package Size MD5 Checksum ADT-21.1.0.zip 13564671 bytes f1ae183891229784bb9c33bcc9c5ef1e - Start Eclipse, then select Help > Install NewSoftware.
- Click Add, in the top-right corner.
- In the Add Repository dialog, click Archive.
- Select the downloaded ADT-21.1.0.zip file and click OK.
- Enter 'ADT Plugin' for the name and click OK.
- In the Available Software dialog, select the checkbox next to Developer Tools and clickNext.
- In the next window, you'll see a list of the tools to be downloaded. ClickNext.
- Read and accept the license agreements, then click Finish. If you get a security warning saying that the authenticity or validity ofthe software can't be established, click OK.
- When the installation completes, restart Eclipse.
To update your plugin once you've installed using the zip file, you will haveto follow these steps again instead of the default update instructions.
Adt Bundle Download
Other install errors
Note that there are features of ADT that require some optionalEclipse packages (for example, WST). If you encounter an error wheninstalling ADT, your Eclipse installion might not include these packages.For information about how to quickly add the necessary packages to yourEclipse installation, see the troubleshooting topicADTInstallation Error: 'requires plug-in org.eclipse.wst.sse.ui'.
For Linux users
If you encounter this error when installing the ADT Plugin for Eclipse:
...then your development machine lacks a suitable Java VM. Installing SunJava 6 will resolve this issue and you can then reinstall the ADTPlugin.
A captive runtime bundle is a package that includes your application code along with a dedicated version of the runtime. An application packaged in this manner uses the bundled runtime instead of the shared runtime installed elsewhere on a user’s computer.
The bundle produced is a self-contained folder of application files on Windows and an .app bundle on Mac OS. You must produce the bundle for a target operating system while running under that operating system. (A virtual machine, such as VMWare, can be used to run multiple operating systems on one computer.)
The application can be run from that folder or bundle without installation.
Benefits
- Produces a self-contained application
- No Internet access required for installation
- Application is isolated from runtime updates
- Enterprises can certify the specific application and runtime combination
- Supports the traditional software deployment model
- No separate runtime redistribution required
- Can use the NativeProcess API
- Can use native extensions
- Can use the File.openWithDefaultApplication() function without restriction
- Can run from a USB or optical disk without installation
Drawbacks
- Critical security fixes are not automatically available to users when Adobe publishes a security patch
- Cannot use the .air file format
- You must create your own installer, if needed
- AIR update API and framework are not supported
- The AIR in-browser API for installing and launching an AIR application from a web page is not supported
- On Windows, file registration must be handled by your installer
- Larger application disk footprint
Creating a captive runtime bundle on Windows
To create a captive runtime bundle for Windows, you must package the application while running under the Windows operating system. Package the application using the ADT bundle target:
This command creates the bundle in a directory named, myApp. The directory contains the files for your application as well as the runtime files. You can run the program directly from the folder. However, to create a program menu entry, register file types, or URI scheme handlers, you must create an installer program that sets the requisite registry entries. The AIR SDK does not include tools for creating such installers, but several third-party options are available, including both commercial and free, open-source installer toolkits.
You can sign the native executable on WIndows, by specifying a second set of signing options after the -target bundle entry on the command line. These signing options identify the private key and associated certificate to use when applying the native Windows signature. (An AIR code signing certificate can typically be used.) Only the primary executable is signed. Any additional executables packaged with your application are not signed by this process.
File type association
To associate your application with public or custom file types on Windows, your installer program must set the appropriate registry entries. The file types should be listed in the fileTypes element of the application descriptor file as well.
For more information about Windows file types, see MSDN Library: File Types and File Associations
URI handler registration
In order for your application to handle the launch of a URL using a given URI scheme, your installer must set the requisite registry entries.
For more information about registering an application to handle a URI scheme, see MSDN Library: Registering an Application to a URL Protocol
Creating a captive runtime bundle on Mac OS X
![Download Adt Bundle For Mac Download Adt Bundle For Mac](/uploads/1/3/4/1/134121107/895213278.jpg)
To create a captive runtime bundle for Mac OS X, you must package the application while running under the Macintosh operating system. Package the application using the ADT bundle target:
This command creates the application bundle named, myApp.app. The bundle contains the files for your application as well as the runtime files. You can run the application by double-clicking the myApp.app icon and install it by dragging it to a suitable location such as the Applications folder. However, to register file types or URI scheme handlers, you must edit the property list file inside the application package.
For distribution, you can create a disk image file (.dmg). The Adobe AIR SDK does not provide tools for creating a dmg file for a captive runtime bundle.
File type association
To associate your application with public or custom file types on Mac OS X, you must edit the info.plist file in the bundle to set the CFBundleDocumentTypes property. See Mac OS X Developer Library: Information Property List Key Reference, CFBundleURLTypes.
URI handler registration
In order for your application to handle the launch of a URL using a given URI scheme, you must edit the info.plist file in the bundle to set the CFBundleURLTypes property. See Mac OS X Developer Library: Information Property List Key Reference, CFBundleDocumentTypes.