logdiag/README.adoc

128 lines
4.1 KiB
Plaintext
Raw Permalink Normal View History

2017-06-19 00:03:44 +02:00
logdiag
=======
'logdiag' is a simple multiplatform schematic editor written in GTK+.
2021-10-23 20:11:10 +02:00
This software has never really been finished, and is no longer being worked on,
although I strive to keep it building on Windows XP and elsewhere.
2017-06-19 00:03:44 +02:00
image::docs/user-guide/logdiag-en.png[align="center"]
2017-06-19 00:03:44 +02:00
Packages
--------
Regular releases are sporadic. git master should be stable enough.
You can get a package with the latest development version using Arch Linux's
https://aur.archlinux.org/packages/logdiag-git[AUR],
or as a https://git.janouch.name/p/nixexprs[Nix derivation].
2017-06-19 00:03:44 +02:00
2021-10-25 18:21:10 +02:00
Windows installers can be downloaded from
https://git.janouch.name/p/logdiag/releases[the Releases page on Gitea].
2017-06-19 00:03:44 +02:00
Requirements
------------
2018-06-27 04:26:43 +02:00
Runtime dependencies: GTK+ >= 3.8, json-glib >= 0.10.4, lua >= 5.2 +
Build dependencies: CMake >= 3.10
2017-06-19 00:03:44 +02:00
2018-06-27 04:26:43 +02:00
Build from source on Unix-like systems
--------------------------------------
2017-06-19 00:03:44 +02:00
First check that you have all the required dependencies installed, including
development packages, if your distribution provides them.
Reserve a directory for an out-of-source build:
$ mkdir build
$ cd build
Let CMake prepare the build. You may change the directory where you want the
application to be installed. The default is _/usr/local_.
$ cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
2021-10-25 18:21:10 +02:00
Now you have two basic choices of installing the application:
2017-06-19 00:03:44 +02:00
2021-10-25 18:21:10 +02:00
1. Using _make install_:
+
2017-06-19 00:03:44 +02:00
# make install
2021-10-25 18:21:10 +02:00
2. Using _cpack_:
+
2017-06-19 00:03:44 +02:00
You have to choose a package format understood by your system package manager.
CMake offers DEB and RPM.
2021-10-25 18:21:10 +02:00
+
2017-06-19 00:03:44 +02:00
After _cpack_ finishes making the package, install this file.
2021-10-25 18:21:10 +02:00
+
2021-07-24 10:08:58 +02:00
$ cpack -G DEB
2017-06-19 00:03:44 +02:00
# dpkg -i logdiag-version-system-arch.deb
Build from source on Windows
----------------------------
2021-10-23 20:27:51 +02:00
_Note that using the current method we're stuck with GTK+ 3.8.2, which works
worse on Windows 10, but better on XP and under WINE._
2017-06-19 00:03:44 +02:00
First, install CMake and MinGW (mingw32-base-bin, mingw32-gettext-dev).
Ensure they're both in your system path. If you want to build an installation
package, also install NSIS. If you want to build within a path containing
spaces, https://gitlab.kitware.com/cmake/cmake/-/issues/22396[fix] your CMake's
2021-10-23 20:27:51 +02:00
FindPkgConfig.cmake module to say:
separate_arguments(_pkgconfig_invoke_result UNIX_COMMAND "${_pkgconfig_invoke_result}")
2017-06-19 00:03:44 +02:00
Run the following command in the directory with source files to automatically
2021-12-28 04:03:54 +01:00
fetch and set up all dependencies:
2017-06-19 00:03:44 +02:00
> cmake -P Win32Depends.cmake
2021-12-28 04:03:54 +01:00
Note that on Windows XP, CMake will fail to download those files, even with
https://emailarchitect.net/easendmail/sdk/html/object_tls12.htm[updates].
You will have to run the script externally.
2021-10-23 20:11:10 +02:00
Reserve a directory for an out-of-source build and let CMake prepare the build:
2017-06-19 00:03:44 +02:00
> mkdir build
> cd build
> cmake .. -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release
Now you can generate a package with CPack. You may choose between:
1. An NSIS-based installation package:
2021-07-24 10:08:58 +02:00
+
2017-06-19 00:03:44 +02:00
> cpack -G NSIS
2. A portable ZIP package:
2021-07-24 10:08:58 +02:00
+
2017-06-19 00:03:44 +02:00
> cpack -G ZIP
By default, that is if you specify no generator, both packages are built.
Cross-compilation for Windows
-----------------------------
The procedure is almost exactly the same as before, including the requirements.
Just install MinGW-w64 and let automation take care of the rest.
$ cmake -P Win32Depends.cmake
$ mkdir build
$ cd build
2021-10-23 20:27:51 +02:00
$ cmake -DCMAKE_TOOLCHAIN_FILE=../ToolchainCrossMinGWW64.cmake \
-DCMAKE_BUILD_TYPE=Release ..
$ cpack
Alternatively, for an unnecessarily bloated MSYS2-based 64-bit build:
2022-08-12 12:33:52 +02:00
$ sh -e Win64Depends.sh
$ cmake -DCMAKE_TOOLCHAIN_FILE=ToolchainCrossWin64.cmake \
-DCMAKE_BUILD_TYPE=Release -B build
$ cmake --build build -- package
2017-06-19 00:03:44 +02:00
2018-06-24 04:24:23 +02:00
Contributing and Support
2017-06-19 00:03:44 +02:00
------------------------
2018-06-24 04:24:23 +02:00
Use https://git.janouch.name/p/logdiag to report any bugs, request features,
or submit pull requests. `git send-email` is tolerated. If you want to discuss
the project, feel free to join me at ircs://irc.janouch.name, channel #dev.
2017-06-19 00:03:44 +02:00
2018-06-24 04:24:23 +02:00
Bitcoin donations are accepted at: 12r5uEWEgcHC46xd64tt3hHt9EUvYYDHe9
2017-06-19 00:03:44 +02:00
License
-------
This software is released under the terms of the 0BSD license, the text of which
is included within the package along with the list of authors.