-
-
Notifications
You must be signed in to change notification settings - Fork 271
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
41 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,41 +1,34 @@ | ||
INSTALLATION | ||
HOW TO INSTALL PEAZIP ON LINUX | ||
|
||
PeaZip is a natively portable application, it means that no installation procedure is strictly required to prepare the system to run it. | ||
The program is released in two ways: as installable package authomatically handling system integration, for ease of use, and as standalone .tar.gz package (peazip_portable). | ||
To install the latter, unpack the content of the .tar.gz package in the directory you prefer; you can move the program's folder in another directory whenever you want (even on network, cloud, or removable paths). | ||
PeaZip is available as pre-built packages on https://peazip.github.io/peazip-linux.html | ||
Packages are built for aarch64 and x86_64, targeting GTK2 and Qt6 widgetsets (experimental GTK3-alpha available for evaluation and debugging purpose), packed as DEB, RPM, and as Portable packages not requiring installation. | ||
|
||
PeaZip Portable contains | ||
pea and peazip binaries | ||
res folder, which contains resources divided by type, and 'portable' empty file marking the package as portable | ||
bin architecture dependent binaries | ||
share non-architecture dependent data such as texts, sample scripts, media, documentation | ||
conf configuration files | ||
HINT: running peazip binary in the console provides more feedback in case of problems running the application, i.e. missing dependencies. | ||
|
||
Installer packages | ||
1) lack (peazip)/res/portable file, triggering the app to use $XDG_CONFIG_HOME/peazip or $HOME/.config/peazip for (peazip)/res/conf configuration files | ||
2) take care to place resources in proper paths depending on the filesystem standards of the target system, the main app folder usually being /usr/lib/peazip | ||
Pre-built packages does not cover all possible combinations of architecture, widgetset, and package format, and are not targeting any specific Linux distribution/version. | ||
Consequently, it is recommended to search for specific installers on your own distro or package manager repositories, and to require inclusion of PeaZip to maintainers of said repositories if a PeaZip package is missing (or outdated) in the repository. | ||
|
||
As alternative: | ||
- PeaZip is available as Flatpak on https://flathub.org/apps/io.github.peazip.PeaZip (Qt6, both for aarch64 and x86_64), or | ||
- PeaZip can be built from sources https://peazip.github.io/peazip-sources.html | ||
|
||
|
||
USAGE | ||
|
||
To start PeaZip doubleclick (or launch by console) "peazip" binary. | ||
If the system finds unresolved dependencies while launching peazip binary for the first time, please follow the instructions of your installer manager to install the needed libraries (may be standard gtk/gdk related libraries, most of times libgdk_pixbuf library). | ||
If the program does not start and the system doesn't give any warning, try launching peazip from a console to get more detailed feedback. | ||
Also, in case of issues please remember to verify that the binaries - pea, peazip and backends in (peazip)/res/bin subdirs - have correct execution rights. | ||
|
||
|
||
SYSTEM INTEGRATION | ||
|
||
Installable packages authomatically handles system integration in Gnome and KDE. | ||
If you are using peazip_portable or if you want to customize the system integration in your desktop environment please follow the instructions in (PeaZip)/res/share/batch/freedesktop_integration folder, which contains example for integrating the application in Gnome (.desktop files and Nautilus scripts), KDE (.desktop files for Konqueror's Action service menu) or other Desktop Environments. | ||
QT VERSION | ||
|
||
Qt6 packages provides libQt6Pas.so which may be required on some machines to run the Qt version of PeaZip. | ||
The binary, or equivalent to libQt6Pas.so, must be installed in /usr/local/lib or equivalent directory, such as /usr/lib. | ||
You can get up to date libQt6Pas.so using distribution-specific tools, i.e. apt-get install package:architecture, or copying the file manually and running ldconfig. | ||
|
||
COMPILE PEAZIP | ||
|
||
PeaZip is developed in FreePascal using Lazarus development environment; to compile the application from source package and for any other information please refer to application's website https://peazip.github.io , or https://peazip.sourceforge.io | ||
OPTIONAL: SYSTEM INTEGRATION | ||
|
||
To integrate PeaZip in context menus and app launchers of Gnome, KDE, and other DE, please refer to the sample .desktop files in (peazip)/res/share/batch/freedesktop_integration directory, and documentation in readme_freedesktop_integration.txt file in same directory. | ||
|
||
|
||
QT VERSION | ||
MORE INFORMATION | ||
|
||
Qt widgetset packages requires Qt5 (Qt 4.3 for legacy 32 bit Linux packages), and needs libQt5Pas.so.1.2.6 often referred as libQt5Pas.so.1 (libqt4intf.so and libqt4pas5 for 32 bit) or equivalent binary installed in /usr/local/lib or equivalent directory, such as /usr/lib or /usr/lib32. | ||
You can get up to date missing libraries using distribution-specific ways, i.e. apt-get install package:architecture, or copy the file manually and run ldconfig | ||
PeaZip sources https://peazip.github.io/peazip-sources.html can be built with Lazarus for Linux. | ||
To add or remove .lpk (Lazarus Packages) dependencies from sources use main menu > Project > Project Inspector. | ||
To manually select the target architecture (i.e. aarch64, x86_64) open main menu, Project > Project Options, Configuration and Target. | ||
To manually set the target widgetset (i.e. GTK2, GTK3, Qt5, Qt6) open main menu, Project > Project Options, Configuration and Target and click "Select other widgetset". | ||
To compile from console, and to build packages, please refer to the readme.txt file in the source package. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,39 @@ | ||
TO INSTALL PEAZIP ON MACOS | ||
HOW TO INSTALL PEAZIP ON MACOS | ||
|
||
1) Open PeaZip's DMG and drop peazip.app in Applications directory | ||
2) Open Terminal, paste and run the following command: | ||
|
||
xattr -dr com.apple.quarantine /Applications/peazip.app | ||
or | ||
sudo xattr -dr com.apple.quarantine /Applications/peazip.app | ||
if current user is not allowed to use xattr command | ||
|
||
Running the aforementioned xattr command is needed to remove the "quarantine" attribute which is automatically applied by Safari to unsigned app packages downloaded from the web; otherwise running PeaZip will result in one of the following error messages: | ||
|
||
"peazip.app is damaged and can’t be opened" | ||
"peazip.app cannot be opened because the developer cannot be verified" | ||
|
||
|
||
OPTIONAL: MACOS SERVICE MENUS | ||
|
||
The link "macOS service menus alias" in the package root contains Automator .workflow service menu scripts for quickly sending the items selected in Finder to main PeaZip functions, in example add to archive, extract, extract here, open file or folder with PeaZip, etc. | ||
|
||
OPTIONAL: MACOS SERVICE MENUS | ||
The link points to the folder with the same name in the installed peazip.app, in | ||
/Applications/peazip.app/Contents/Resources/share/batch/macOS service menus/ | ||
So, applying the correct attributes to the app with xattr (as explained in the previous point) also applies the attributes to those items, allowing them to be correctly installed. | ||
|
||
To install a .workflow item, double-click on it. | ||
To uninstall a .workflow item, follow system's instruction from context menu customization entry or simply delete or move it from user's home folder ˜/Library/Services/ directory (which is hidden by default, as alternative to Finder it can be conveniently browsed with PeaZip). | ||
|
||
The directory "macOS service menus" contains .workflow scripts of context menu items to quickly send items selected in Finder to to main PeaZip functions: add to archive, extract (with full options), extract here (without further interaction), and open file or folder with PeaZip. | ||
To install a .workflow item, double-click on it. | ||
To uninstall a .workflow item, follow system's instruction from context menu customization entry or simply delete it from ˜/Library/Services/ directory. | ||
|
||
OPTIONAL: CUSTOMIZE APP ICON | ||
|
||
The icon displayed while running the app is hardcoded at compile time, it can be changed with Lazarus IDE from Project Options (applies globally to all forms) or changing the icon for each form. | ||
The icon displayed in the dock (while app is not running), in Launcher, and in Finder can be customized replacing the app icon (i.e. from Get Info) with one of the .icns files provided in /Applications/peazip.app/Contents/Resources/share/icons folder inside peazip.app (rightclick the app and select "show content" in Finder). | ||
|
||
|
||
MORE INFORMATION | ||
|
||
PeaZip is available built for aarch64 and Intel architectures on https://peazip.github.io/peazip-macos.html | ||
The application's binaries are not signed by a registered Apple developer account: M1 version is simply ad-hoc signed, Intel version is not signed. | ||
M1 SoC can run both aarch64 (native) and Intel (using Rosetta 2 emulation layer), Intel-based Macintosh systems can only run Intel version. | ||
M1 SoC can run bot aarch64 (native) and Intel (using Rosetta 2 emulation layer), Intel-based Macintosh systems can only run Intel version. | ||
|
||
PeaZip sources https://peazip.github.io/peazip-sources.html can be built with Lazarus for macOS, sources are tested for Cocoa widget set. | ||
To manually select the target architecture open main menu, Project > Project Options, Configuration and Target, set Darwin as destination OS, and aarch64 as destination CPU family if compiling for machines with M1 Apple Silicon chip, or x86_64 if compiling for Intel-based Apple machines. | ||
To manually select the target architecture open main menu, Project > Project Options, Configuration and Target, set Darwin as destination OS, and aarch64 as destination CPU family if compiling for machines with M1 Apple Silicon chip, or x86_64 if compiling for Intel-based Apple machines. |