Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
stacker:docs:linux_installation_instructions [2013/01/27 18:58] rjlittlefield |
stacker:docs:linux_installation_instructions [2020/03/04 23:00] rjlittlefield |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Linux Installation Instructions ====== | ====== Linux Installation Instructions ====== | ||
- | The current distribution package for Linux consists of a .zip archive that unpacks to produce a hierarchy of files as follows: | + | The current distribution package for Linux consists of a .zip archive that unzips to produce a hierarchy of files as follows: |
<code> | <code> | ||
ZereneStacker top level directory | ZereneStacker top level directory | ||
- | ZereneStacker.bsh launch script | + | ZereneStacker executable launcher |
+ | ZereneStacker.bsh launch script (provided for backward compatibility) | ||
+ | zerenstk.ini launch template, expanded by the launcher based on user configuration settings | ||
ZereneStacker.jar jar containing the application | ZereneStacker.jar jar containing the application | ||
JREextensions directory containing numerous .jar files | JREextensions directory containing numerous .jar files | ||
- | jre directory containing a Sun Java Runtime Environment for Linux | + | jre directory containing a Java Runtime Environment for Linux |
(32-bit or 64-bit as appropriate) | (32-bit or 64-bit as appropriate) | ||
</code> | </code> | ||
+ | The executable launcher, ZereneStacker, is written so that it can be accessed in any manner, including by symbolic link or being placed on the PATH. If you want to use a JRE other than the one provided with the distribution, just edit the zerenstk.ini template as desired. | ||
- | The launch script assumes that the archive is unpacked into the user's home directory. | + | The launch script ZereneStacker.bsh is written so that the package will run no matter where it is placed. You can launch it from the desktop or a file browser by double-clicking it and confirming either "Run" or "Run in Terminal". Alternatively, you can execute it from a Terminal window as ZereneStacker/ZereneStacker.bsh (plus whatever path prefix is required to find the ZereneStacker directory). |
- | If it is unpacked to a different location, then you must edit the ZereneStacker.bsh launch script | + | For your convenience in using the package later, you may also want to create a "launcher" icon that will provide launch by double-click without the confirming dialog. The procedure for doing that depends on what version of Linux and what desktop manager you're using. Some helpful guidance is provided [[http://askubuntu.com/questions/64222/how-can-i-create-launchers-on-my-desktop|HERE]] at askubuntu.com. |
- | so that the symbol appdir points to the location where you unpacked the .zip file. | + | |
- | + | ||
- | As distributed, the script says | + | |
- | <code>appdir="$HOME/ZereneStacker"</code> | + | |
- | + | ||
- | If you download and unpack the archive to your Desktop, then the script should be edited to say | + | |
- | <code>appdir="$HOME/Desktop/ZereneStacker"</code> | + | |
- | + | ||
- | With appdir properly set, executing the launch script should start Zerene | + | |
- | Stacker, producing first a splash screen and then a full GUI as shown | + | |
- | in the online documentation. | + | |
+ | Troubleshooting: We have seen a couple of things go wrong with Linux installations. | ||
+ | * In some Linux configurations, the .zip file will not automatically unzip. Instead, double-clicking on the .zip file simply opens a sort of archive manager that lets you look into the .zip archive as if it were a tree of ordinary files. You will not be able to run ZereneStacker in that environment. In that case you have to manually unzip the archive, using command line "unzip" or your favorite zip archive manager. \\ \\ | ||
+ | * Sometimes files do not retain their proper "execute" permissions after unzipping. In that case we suggest explicitly setting the required execute permissions using the following command line script: | ||
+ | <code> | ||
+ | chmod +x ZereneStacker/*.zslinux | ||
+ | chmod +x ZereneStacker/ZereneStacker.bsh | ||
+ | chmod +x ZereneStacker/ZereneStacker | ||
+ | chmod +x ZereneStacker/jre/bin/* | ||
+ | chmod +x ZereneStacker/jre/lib/jspawnhelper | ||
+ | </code> | ||