p
/
logdiag
1
1
Fork 0
Code Issues Pull Requests Releases 4 Wiki Activity
Schematic editor
207 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 b5ff3b5bbb Don't emit changes when reading. 
When the value for a property isn't present in it's JsonObject,
it can be assigned upon reading. Previously this could generate
history events even when just viewing an old diagram with some
of newer properties missing.

Modify the code, so setting to default doesn't count as a change
anymore.
 		2011-02-19 22:49:20 +01:00
cmake Change the way translations are done. 2011-02-12 18:40:16 +01:00
liblogdiag Don't emit changes when reading. 2011-02-19 22:49:20 +01:00
po Update translations. 2011-02-13 20:55:03 +01:00
share Change voltage source symbols. 2011-02-19 22:49:20 +01:00
src Reset view to center for new diagrams. 2011-02-19 22:49:20 +01: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 Rename LdCanvas to LdDiagramView. 2011-02-19 22:49:20 +01:00
LICENSE Set up the project for NSIS. 2011-01-22 20:18:46 +01:00
NEWS Bump version to 0.1.0. 2011-02-07 20:46:29 +01:00
README.md Fix README. 2011-02-19 22:48:22 +01:00
Win32Depends.cmake Update json-glib checksums. 2011-02-12 18:54:54 +01:00
config.h.in Change the way translations are done. 2011-02-12 18:40:16 +01: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.
    $ 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.