Difference between revisions of "Adobe AIR"

From ArchWiki
Jump to: navigation, search
(Making it executable)
(Undo revision 442977 by Lahwaacz.bot (talk) bug)
 
(11 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
[[Category:Development]]
 
[[Category:Development]]
[[Category:Internet Applications]]
+
[[Category:Internet applications]]
 
[[ja:Adobe AIR]]
 
[[ja:Adobe AIR]]
 
[[zh-CN:Adobe AIR]]
 
[[zh-CN:Adobe AIR]]
Line 6: Line 6:
  
 
==Installing Adobe AIR ==
 
==Installing Adobe AIR ==
Install [https://aur.archlinux.org/packages.php?ID=25633&comments=all adobe-air-sdk] from the [[AUR]].
+
Install [https://aur.archlinux.org/packages/adobe-air-sdk/?comments=all adobe-air-sdk] from the [[AUR]].
  
 
==Installing an AIR Application==
 
==Installing an AIR Application==
Line 14: Line 14:
  
 
===Making it executable===
 
===Making it executable===
You can also make an executable by creating a file in {{ic|/usr/bin}}:
+
You can also make an executable by creating a file in {{ic|/usr/local/bin}}:
 
{{bc|
 
{{bc|
  #! /bin/sh
+
  #!/usr/bin/sh
  /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/wimp/
+
  /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/
 
}}
 
}}
 
The app might need parameters (voddler) so then the script can look like:
 
The app might need parameters (voddler) so then the script can look like:
 
{{bc|
 
{{bc|
  #! /bin/sh
+
  #!/usr/bin/sh
  /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/wimp/ -- $1 $2 $3 $4
+
  /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/ -- ${@}
 
}}
 
}}
 
Then ''chmod'' the file so that it can execute:
 
Then ''chmod'' the file so that it can execute:
Line 31: Line 31:
 
===Removing the application===
 
===Removing the application===
 
Delete the application folder in {{ic|/opt/airapps}}. Also delete the executable if you created one.
 
Delete the application folder in {{ic|/opt/airapps}}. Also delete the executable if you created one.
 +
 +
===Running binaries that use AIR===
 +
 +
Some applications using Adobe AIR can come with their own binaries included. In this case, it's often better to run these binaries, rather than bypassing them using adl, to not lose any extra functionality these binaries might provide. These binaries will require some work however, before they can be used with the Adobe AIR SDK.
 +
 +
First of all, binaries will look for Adobe AIR, rather than the Adobe AIR SDK. There seems to be no way to change where to look, so you're going to have to symlink the Adobe AIR runtime provided with the SDK to the default location that binaries follow:
 +
 +
{{bc| # ln -s /opt/adobe-air-sdk/runtimes/air/linux/Adobe\ AIR/ /opt/Adobe\ AIR}}
 +
With this, the binaries should be able to detect your Adobe AIR installation. It will leave you with two Adobe AIR folders in {{ic | /opt}}, which is dirty but there seems to be no way around this for now.
 +
 +
Another problem you'll run into is that whenever the AIR runtime starts a process, it'll check whether you have accepted the EULA, something that is not included with the SDK. Since it can't determine that you did, it then tries to run the Adobe AIR Updater, which is ALSO not included in the SDK runtime, causing the binary to fail and hang. To avoid this you're going to have to manually accept the EULA.
 +
 +
{{Warning | By creating the following file you are most likely accepting the [http://www.adobe.com/products/eulas/air_eula.html Adobe AIR End User License Agreement]. Make sure to read this agreement, and do not perform this work-around if you do not agree with it.}}
 +
 +
 +
To manually accept the EULA, use this command:
 +
 +
{{bc|
 +
echo -n 2 > ~/.appdata/Adobe/AIR/eulaAccepted
 +
}}
 +
 +
After this, you should clear the check and the binary should run normally.
 +
 +
== App-specific troubleshooting ==
 +
=== ZinioReader4 ===
 +
The app doesn't start out of the box if you are not using [[GNOME]] or [[KDE]] on a 32 bit installation.
 +
 +
Required packages: {{Pkg|libgnome}}, {{Pkg|libgnome-keyring}}, {{Pkg|gnome-keyring}} and {{AUR|lib32-libgnome-keyring}}{{Broken package link|{{aur-mirror|lib32-libgnome-keyring}}}} (only on x86_64)
 +
 +
Run with the command:
 +
 +
{{bc | DESKTOP_SESSION&#61;"gnome" /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/ZinioReader4/META-INF/AIR/application.xml /opt/airapps/ZinioReader4/
 +
}}

Latest revision as of 09:10, 25 July 2016

Adobe Integrated Runtime (AIR) is a cross-platform runtime environment developed by Adobe Systems for building rich Internet applications using Adobe Flash, Adobe Flex, HTML, or Ajax, that can be deployed as desktop applications.

Installing Adobe AIR

Install adobe-air-sdk from the AUR.

Installing an AIR Application

Download the application, and unzip it to /opt/airapps/<appname>. To run it you can use the command

$ /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/

Making it executable

You can also make an executable by creating a file in /usr/local/bin:

 #!/usr/bin/sh
 /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/

The app might need parameters (voddler) so then the script can look like:

 #!/usr/bin/sh
 /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/ -- ${@}

Then chmod the file so that it can execute:

$ chmod +x filename

Now you have installed an application in AIR. Yes it is this silly :P

Removing the application

Delete the application folder in /opt/airapps. Also delete the executable if you created one.

Running binaries that use AIR

Some applications using Adobe AIR can come with their own binaries included. In this case, it's often better to run these binaries, rather than bypassing them using adl, to not lose any extra functionality these binaries might provide. These binaries will require some work however, before they can be used with the Adobe AIR SDK.

First of all, binaries will look for Adobe AIR, rather than the Adobe AIR SDK. There seems to be no way to change where to look, so you're going to have to symlink the Adobe AIR runtime provided with the SDK to the default location that binaries follow:

 # ln -s /opt/adobe-air-sdk/runtimes/air/linux/Adobe\ AIR/ /opt/Adobe\ AIR

With this, the binaries should be able to detect your Adobe AIR installation. It will leave you with two Adobe AIR folders in /opt, which is dirty but there seems to be no way around this for now.

Another problem you'll run into is that whenever the AIR runtime starts a process, it'll check whether you have accepted the EULA, something that is not included with the SDK. Since it can't determine that you did, it then tries to run the Adobe AIR Updater, which is ALSO not included in the SDK runtime, causing the binary to fail and hang. To avoid this you're going to have to manually accept the EULA.

Warning: By creating the following file you are most likely accepting the Adobe AIR End User License Agreement. Make sure to read this agreement, and do not perform this work-around if you do not agree with it.


To manually accept the EULA, use this command:

echo -n 2 > ~/.appdata/Adobe/AIR/eulaAccepted

After this, you should clear the check and the binary should run normally.

App-specific troubleshooting

ZinioReader4

The app doesn't start out of the box if you are not using GNOME or KDE on a 32 bit installation.

Required packages: libgnome, libgnome-keyring, gnome-keyring and lib32-libgnome-keyringAUR[broken link: archived in aur-mirror] (only on x86_64)

Run with the command:

 DESKTOP_SESSION="gnome" /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/ZinioReader4/META-INF/AIR/application.xml /opt/airapps/ZinioReader4/