logdiag/README.md

99 lines
2.5 KiB
Markdown
Raw Normal View History

# logdiag
2012-10-10 21:05:39 +02:00
logdiag is a simple multiplatform schematic editor written in GTK+.
2012-10-10 21:05:39 +02:00
__This software is considered to be of alpha quality and isn't recommended for
2012-01-29 22:43:20 +01:00
regular usage.__
2011-02-07 19:10:29 +01:00
## Requirements
2012-01-29 22:43:20 +01:00
Runtime dependencies:
2015-01-20 09:48:52 +01:00
- GTK+ >= 3.8
- json-glib >= 0.10.4
2015-01-18 23:33:21 +01:00
- lua = 5.2
2012-01-29 22:43:20 +01:00
Build dependencies:
2015-01-18 23:33:21 +01:00
- CMake >= 2.8
2011-02-07 19:10:29 +01:00
## Installation from sources on Unix-like systems
2012-01-29 22:43:20 +01:00
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
2012-01-29 22:43:20 +01:00
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
2012-01-29 22:43:20 +01:00
#### Using _cpack_
2012-01-29 22:43:20 +01:00
You have to choose a package format understood by your system package manager.
CMake offers DEB and RPM.
2012-01-29 22:43:20 +01:00
After _cpack_ finishes making the package, install this file.
2012-01-29 22:43:20 +01:00
$ fakeroot cpack -G DEB
2012-10-10 21:05:39 +02:00
# dpkg -i logdiag-version-system-arch.deb
2015-01-18 23:33:21 +01:00
Leave out the fakeroot for CMake >= 2.8.9, it's been fixed since.
2011-07-05 13:12:34 +02:00
## Building from sources on Windows
2015-01-28 00:16:41 +01:00
First install CMake >= 3.1 and MinGW. Add both to your system path. If you want
to build an installation package, also install NSIS.
2012-01-29 22:43:20 +01:00
Run the following command in the directory with source files to automatically
2012-10-10 21:05:39 +02:00
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
2012-01-29 22:43:20 +01:00
Reserve a directory for an out-of-source build:
> mkdir build
> cd build
2012-01-29 22:43:20 +01:00
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:
2012-01-29 22:43:20 +01:00
> cpack -G NSIS
2012-01-29 22:43:20 +01:00
2. A portable ZIP package:
2012-01-29 22:43:20 +01:00
> cpack -G ZIP
2012-01-29 22:43:20 +01:00
By default, that is if you specify no generator, both packages are built.
## Cross-compiling for Windows
2015-01-28 00:16:41 +01:00
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
2015-01-28 00:16:41 +01:00
$ cpack