![]() ![]() (peazip sources)/dev/project_demo_lib.lpi: an OPTIONAL demo application using PEA sources as a library, this is only meant as example and it is not required by PeaZip (peazip sources)/dev/project_peach.lpi: originally PEACH, PEAlaunCHer, that compiles to the main executable PeaZip and act as GUI frontend for PEA, 7z and other utilities (peazip sources)/dev/project_pea.lpi: PEA, the actual engine for PEA file format support (peazip sources)/dev subdirectory contains sources of the project To integrate the app in the target system (or for using PeaZip from scripts) please refer to examples in (peazip sources)/res/share/batch directory. non-binary resources collected in (peazip sources)/res/share directory can be saved in /usr/share, or even further distinction can be made between subdirectories containing application texts and graphic. If the target system needs to enforce stringent Filesystem Hierarchy Standard rules, you can replace resources in the package with links, saving the actual resources in the appropriate branch of the filesystem - e.g. in /usr/lib on most Linux distributions). To create an installer for PeaZip you will then simply need to put the root folder of the app into the package, and instruct the installer to copy it to the appropriate location for the target system (e.g. in $XDG_CONFIG_HOME for most *x-like systems). To transform the Portable package in a non-portable one, simply delete (peazip sources)/res/portable file (which is plainly an empty file): in this way PeaZip will save its configuration to the appropriate user-specific location for the host system (e.g. You have now a working PeaZip Portable package, which saves the app's configuration in (peazip sources)/res/conf directory: you can simply compress the root folder of the app and move the application and its configuration altogether where you need it.Ħ) CREATE AN INSTALLABLE PEAZIP PACKAGE (OPTIONAL) This directory already contains all the needed files. (peazip sources)/res/share directory already contains non-binary, non-platform-dependent resources needed by PeaZip, as graphic, texts, help file, and sample scripts. 7z in (peazip sources)/res/bin/7z subdirectory. Third party binaries are NOT provided with PeaZip source package because they are platform specific: you need to download the appropriate binary for the target OS and CPU architecture, and save them in the subdirectories of the bin folder - e.g. (peazip sources)/res/bin directory will contain third party binaries (e.g. You will no longer need (peazip sources)/dev directory afterwards. Place pea and peazip binaries (and dragdropfilesdll.dll on Windows systems) in (peazip sources) root. lpi files in Lazarus and follow suggestions of the DETAILED GUIDE section. Replace (peazip sources) with fill qualified path to PeaZip source's directory. Replace lazbuild with full qualified path to lazbuild binary if needed. Lazbuild (peazip sources)/dev/dragdropfilesdll/dragdropfilesdll.lpi (only needed for Windows systems) Lazbuild (peazip sources)/dev/project_pea.lpi Lazbuild (peazip sources)/dev/project_peach.lpi In case of issues with installation (step 1) or use (step 2) of Lazarus, its community can be reached through the forum of the aforementioned domain and is usually very helpful and friendly. ![]() This section provides a quick step-by-step to-do list for building PeaZip from source package, anyway it is recommended to also read the following DETAILED GUIDE section in order to understand in details the process of building and deploying a custom PeaZip package, possibly targeting new Operating Systems, CPU architectures, and package management systems. QUICK START-UP GUIDE TO BUILD A PEAZIP PACKAGE (peazip sources)/res contain resources needed to run PeaZip and deploy it as portable or installable application ![]() (peazip sources)/dev subdirectory contains sources for compiling and building PeaZip's own binaries ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |