Schematic editor
Go to file
Přemysl Eric Janouch d55422e0a5 Travis CI: Try making the tests work 2015-02-08 16:26:45 +01:00
cmake Fix Debian build 2015-01-20 07:40:46 +01:00
docs/user-guide Add a user guide for Microsoft Windows. 2011-03-07 17:29:26 +01:00
liblogdiag Try making it build with GTK+ 3.4 2015-02-08 15:48:01 +01:00
po Fix the make-template.sh script. 2012-01-29 21:48:17 +01:00
share Support multiple filenames on command line. 2012-10-09 18:03:28 +02:00
src Update copyright years 2015-01-20 23:19:06 +01:00
tests Travis CI: Try making the tests work 2015-02-08 16:26:45 +01:00
vera++@45f3ab870d Update vera++ 2015-01-18 23:29:53 +01:00
.gitignore Ignore Qt Creator settings file in the tree. 2011-07-05 13:11:49 +02:00
.gitmodules Update vera++ 2015-01-18 23:29:53 +01:00
.travis.yml Travis CI: Try making the tests work 2015-02-08 16:26:45 +01:00
CMakeLists.txt Fix to work on Windows XP 2015-01-28 00:16:41 +01:00
LICENSE Update copyright years 2015-01-20 23:19:06 +01:00
NEWS Update NEWS 2015-01-21 20:33:23 +01:00
README.md Fix to work on Windows XP 2015-01-28 00:16:41 +01:00
ToolchainDebianMinGW.cmake Make MinGW{,-w64} crosscompilation working. 2013-01-08 02:46:07 +01:00
ToolchainDebianMinGWW64.cmake Make MinGW{,-w64} crosscompilation working. 2013-01-08 02:46:07 +01:00
Win32Depends.cmake Fix to work on Windows XP 2015-01-28 00:16:41 +01:00
config.h.in Cleanup 2015-01-21 20:25:59 +01:00

README.md

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.

Requirements

Runtime dependencies:

  • GTK+ >= 3.8
  • json-glib >= 0.10.4
  • lua = 5.2

Build dependencies:

  • CMake >= 2.8

Installation from sources on Unix-like systems

First check that you have all the required dependencies installed, including all 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.

Building from sources on Windows

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

  2. A portable ZIP package:

    cpack -G ZIP

By default, that is if you specify no generator, both packages are built.

Cross-compiling 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