Schematic editor
Go to file
Přemysl Eric Janouch b5af31b048
Fix Lua cross-build, bump the Win32 version
Something has changed and it could no longer find the include files.
2018-06-25 02:34:35 +02:00
cmake Make gtk-doc work again 2018-06-24 23:27:26 +02:00
docs/user-guide Add a user guide for Microsoft Windows. 2011-03-07 17:29:26 +01:00
liblogdiag Make gtk-doc work again 2018-06-24 23:27:26 +02:00
po Relicense to 0BSD, update mail address 2018-06-24 04:22:37 +02:00
share Support multiple filenames on command line. 2012-10-09 18:03:28 +02:00
src Fix and update LICENSE 2017-02-03 23:06:48 +01:00
tests Fix and update LICENSE 2017-02-03 23:06:48 +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 Fix Lua cross-build, bump the Win32 version 2018-06-25 02:34:35 +02:00
LICENSE Relicense to 0BSD, update mail address 2018-06-24 04:22:37 +02:00
NEWS Update NEWS 2015-01-21 20:33:23 +01:00
README.adoc Update README 2018-06-24 04:24:23 +02:00
ToolchainDebianMinGW.cmake Streamline README 2017-06-19 00:03:44 +02:00
ToolchainDebianMinGWW64.cmake Streamline README 2017-06-19 00:03:44 +02:00
Win32Depends.cmake Fix Lua cross-build, bump the Win32 version 2018-06-25 02:34:35 +02:00
config.h.in Cleanup 2015-01-21 20:25:59 +01:00
logdiag.png Streamline README 2017-06-19 00:03:44 +02:00

README.adoc

logdiag

logdiag is a simple multiplatform schematic editor written in GTK+.

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

logdiag

Packages

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

Requirements

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

Build from source on Unix-like

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.

$ 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, its been fixed since.

Build from source on Windows

Note that with the current method were 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, its 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 \
  -DCMAKE_BUILD_TYPE=Release
$ cpack

Contributing and Support

Use https://git.janouch.name/p/logdiag 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://irc.janouch.name, channel #dev.

Bitcoin donations are accepted at: 12r5uEWEgcHC46xd64tt3hHt9EUvYYDHe9

License

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.