Schematic editor
Go to file
Přemysl Eric Janouch b2223d6595 Integrate GSettings, remember View settings.
The org.logdiag ID has been chosen as I haven't found any specific rules
and com.github.logdiag seems not to be future-proof. This domain remains
available so far, anyway.

The schemas are compiled only when installed directly to CMAKE_INSTALL_PREFIX
to the root filesystem. When invoking `make install` with DESTDIR, only
the XML files are copied over as the schemas would have to be recompiled
later anyway.
2011-06-12 10:05:16 +02:00
cmake Change the way translations are done. 2011-02-12 18:40:16 +01:00
docs/user-guide Add a user guide for Microsoft Windows. 2011-03-07 17:29:26 +01:00
liblogdiag Change the cursor when scrolling the view. 2011-06-09 21:56:38 +02:00
po Fix make-template.sh. 2011-06-11 11:46:43 +02:00
share Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02:00
src Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02:00
tests Fix undoing, create a unit test for history. 2011-02-05 19:47:07 +01:00
.gitignore Remove marshallers from the tree and ignore them. 2011-01-27 18:56:41 +01:00
CMakeLists.txt Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02:00
LICENSE Set up the project for NSIS. 2011-01-22 20:18:46 +01:00
NEWS Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02:00
README.md Fix .deb package generation. 2011-06-09 21:11:22 +02:00
Win32Depends.cmake Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02:00
config.h.in Integrate GSettings, remember View settings. 2011-06-12 10:05:16 +02:00

README.md

logdiag

logdiag is a schematic editor written in GTK+.

This software is considered to be alpha quality and cannot be recommended
for regular usage.

Requirements

Runtime dependencies:

  • GTK+ >= 2.12
  • json-glib >= 0.10.4
  • lua = 5.1
  • librsvg >= 2.0

Build dependencies:

  • CMake >= 2.6

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:

  1. Using make install:
    # make install

  2. 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-0.0-Linux-x86_64.deb

Building from sources on Windows

First install CMake 2.8 and MinGW. Add both to the 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:
> 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.