Přemysl Eric Janouch
f9f1c830f8
We don't depend on any proprietary services no longer. I'll have to make my own replacements with blackjack and hookers. Until then, the file stays in the commit log as an example. |
||
|---|---|---|
| cmake | ||
| docs/user-guide | ||
| liblogdiag | ||
| po | ||
| share | ||
| src | ||
| tests | ||
| vera++@45f3ab870d | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| LICENSE | ||
| NEWS | ||
| README.adoc | ||
| ToolchainDebianMinGW.cmake | ||
| ToolchainDebianMinGWW64.cmake | ||
| Win32Depends.cmake | ||
| config.h.in | ||
| logdiag.png | ||
README.adoc
logdiag
logdiag is a simple multiplatform schematic editor written in GTK+.
This software is considered to be of alpha quality and isn’t recommended for regular usage.
Packages
Regular releases are sporadic. git master should be stable enough. You can get a package with the latest development version from Archlinux’s AUR.
Requirements
Runtime dependencies: GTK+ >= 3.8, json-glib >= 0.10.4, lua = 5.2
Build dependencies: CMake >= 2.8
Build from source on Unix-like
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
Now you have two basic choices of installing the application.
Using make install
# make install
Using cpack
You have to choose a package format understood by your system package manager. CMake offers DEB and RPM.
After cpack finishes making the package, install this file.
$ fakeroot cpack -G DEB # dpkg -i logdiag-version-system-arch.deb
Leave out the fakeroot for CMake >= 2.8.9, it’s been fixed since.
Build from source on Windows
Note that with the current method we’re stuck with GTK+ 3.10.4 at best.
First install CMake >= 3.1 and MinGW. Add both to your system path. If you want to build an installation package, also install NSIS.
Run the following command in the directory with source files to automatically fetch and setup all dependencies (contact me if the script becomes obsolete, it’s easy to fix but I usually update it only just a short while before releasing a new version in order to resolve compatibility issues):
> cmake -P Win32Depends.cmake
Reserve a directory for an out-of-source build:
> mkdir build > cd build
Let CMake prepare the build:
> cmake .. -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release
Now you can generate a package with CPack. You may choose between:
-
An NSIS-based installation package:
> cpack -G NSIS
-
A portable ZIP package:
> 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 $ cmake .. \ -DCMAKE_TOOLCHAIN_FILE=../ToolchainDebianMinGWW64.cmake \ -DCMAKE_BUILD_TYPE=Release $ cpack
Contributing and Support
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.
Bitcoin donations are accepted at: 12r5uEWEgcHC46xd64tt3hHt9EUvYYDHe9
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.