wok-current view adobe-air-sdk/description.txt @ rev 21867
compile scilab with gcc83
| author | Hans-G?nter Theisgen |
|---|---|
| date | Tue Sep 24 16:35:35 2019 +0100 (2019-09-24) |
| parents | |
| children |
line source
1 [Adobe Integrated Runtime (AIR)](https://en.wikipedia.org/wiki/Adobe_Integrated_Runtime)
2 is a cross-platform runtime environment developed by Adobe Systems for building
3 rich Internet applications using Adobe Flash, Adobe Flex, HTML, or Ajax, that
4 can be deployed as desktop applications.
7 Installing an AIR Application
8 -----------------------------
10 Download the application, and unzip it to `/opt/airapps/<appname>`. To run it
11 you can use the command
13 $ /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/
16 Making it executable
17 --------------------
19 You can also make an executable by creating a file in /usr/local/bin:
21 #!/usr/bin/sh
22 /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/
24 The app might need parameters (voddler) so then the script can look like:
26 #!/usr/bin/sh
27 /opt/adobe-air-sdk/bin/adl -nodebug /opt/airapps/<Application name>/META-INF/AIR/application.xml /opt/airapps/<Application name>/ -- ${@}
29 Then chmod the file so that it can execute:
31 $ chmod +x filename
33 Now you have installed an application in AIR. Yes it is this silly :P
36 Removing the application
37 ------------------------
39 Delete the application folder in `/opt/airapps`. Also delete the executable if
40 you created one.
43 Running binaries that use AIR
44 -----------------------------
46 Some applications using Adobe AIR can come with their own binaries included. In
47 this case, it's often better to run these binaries, rather than bypassing them
48 using adl, to not lose any extra functionality these binaries might provide.
49 These binaries will require some work however, before they can be used with the
50 Adobe AIR SDK.
52 First of all, binaries will look for Adobe AIR, rather than the Adobe AIR SDK.
53 There seems to be no way to change where to look, so you're going to have to
54 symlink the Adobe AIR runtime provided with the SDK to the default location
55 that binaries follow:
57 # ln -s /opt/adobe-air-sdk/runtimes/air/linux/Adobe\ AIR/ /opt/Adobe\ AIR
59 With this, the binaries should be able to detect your Adobe AIR installation.
60 It will leave you with two Adobe AIR folders in /opt, which is dirty but there
61 seems to be no way around this for now.
63 Another problem you'll run into is that whenever the AIR runtime starts a
64 process, it'll check whether you have accepted the EULA, something that is not
65 included with the SDK. Since it can't determine that you did, it then tries to
66 run the Adobe AIR Updater, which is ALSO not included in the SDK runtime,
67 causing the binary to fail and hang. To avoid this you're going to have to
68 manually accept the EULA.
70 Warning: By creating the following file you are most likely accepting the
71 [Adobe AIR End User License Agreement](http://www.adobe.com/products/eulas/air_eula.html).
72 Make sure to read this agreement, and do not perform this work-around if you do
73 not agree with it.
76 To manually accept the EULA, use this command:
78 echo -n 2 > ~/.appdata/Adobe/AIR/eulaAccepted
80 After this, you should clear the check and the binary should run normally.
82 ---
84 This information has been shamelessly copied from this page:
85 https://wiki.archlinux.org/index.php/Adobe_AIR
87 Content is available under GNU Free Documentation License 1.3 or later unless
88 otherwise noted.