p
/
logdiag
1
1
Fork 0
Code Issues Pull Requests Releases 4 Wiki Activity
Schematic editor
307 Commits 1 Branch 6 Tags 2.4 MiB
C 84%
CMake 9.7%
Lua 5.4%
Shell 0.9%
Go to file
Přemysl Eric Janouch c41f3ae529 Switch to GTK3 via pkg-config, start the port 2015-01-19 00:02:48 +01:00
cmake Bump CMake to 2.8 for no obvious reason 2015-01-18 22:47:00 +01:00
docs/user-guide Add a user guide for Microsoft Windows. 2011-03-07 17:29:26 +01:00
liblogdiag Switch to GTK3 via pkg-config, start the port 2015-01-19 00:02:48 +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 Show something more helpful on file open error. 2012-10-09 18:06:00 +02:00
tests Fix undoing, create a unit test for history. 2011-02-05 19:47:07 +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
CMakeLists.txt Switch to GTK3 via pkg-config, start the port 2015-01-19 00:02:48 +01:00
LICENSE Update copyrights. 2012-10-08 10:35:09 +02:00
NEWS Update NEWS. 2012-10-09 07:06:52 +02:00
README.md Update the README 2015-01-18 23:33:21 +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 Make MinGW{,-w64} crosscompilation working. 2013-01-08 02:46:07 +01:00
config.h.in Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02: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+ >= 2.12
  • 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 2.8 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.