Schematic editor
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Přemysl Janouch cc47064379
CMakeLists.txt: use HTTPS in project URL
11 months ago
cmake Make gtk-doc work again 11 months ago
docs/user-guide Bump version, update NEWS 11 months ago
liblogdiag Fix assertion failures on quitting 11 months ago
po Update .po files 11 months ago
share Support multiple filenames on command line. 6 years ago
src Fix compiler warning 11 months ago
tests Fix and update LICENSE 2 years ago
vera++ @ 45f3ab870d Update vera++ 4 years ago
.gitignore Ignore Qt Creator settings file in the tree. 8 years ago
.gitmodules Update vera++ 4 years ago
CMakeLists.txt CMakeLists.txt: use HTTPS in project URL 11 months ago
LICENSE Update copyright years 11 months ago
NEWS Bump version, update NEWS 11 months ago
README.adoc Bump version, update NEWS 11 months ago
ToolchainDebianMinGW.cmake Streamline README 2 years ago
ToolchainDebianMinGWW64.cmake Streamline README 2 years ago
Win32Depends.cmake Find a better solution to the Lua situation 11 months ago Cleanup 4 years ago


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.



Regular releases are sporadic. git master should be stable enough. You can get a package with the latest development version from Archlinux's AUR.


Runtime dependencies: GTK+ >= 3.8, json-glib >= 0.10.4, lua >= 5.2
Build dependencies: CMake >= 2.8

Build from source on Unix-like systems

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.


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:

  1. An NSIS-based installation package:

> cpack -G NSIS
  1. 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 \
$ cpack

Contributing and Support

Use 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://, channel #dev.

Bitcoin donations are accepted at: 12r5uEWEgcHC46xd64tt3hHt9EUvYYDHe9


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.