KLayout Main Sources
Go to file
Matthias Koefferlein 4a8c4fef35 Generalized run_ut step in Jenkinsfile. 2018-06-24 12:30:17 +02:00
etc Updated CONTRIB file, preparations for RPM building. 2017-09-10 17:42:38 +00:00
macbuild MacPorts has released Qt 5.10.1. 2018-04-09 20:06:03 +09:00
scripts WIP: speedup for CI development, fixed deb package (python needs to be part of dependency), fixed gcc build with Python3 2018-06-21 22:18:17 +02:00
src WIP: added force-link to rdb Python module so the rdb library is always linked 2018-06-22 00:02:27 +02:00
testdata WIP: fixed some build issues, removed some link dependencies which causes issues on Windows. 2018-06-19 20:31:55 +02:00
.gitignore Renamed pykl to klayout - because of name clash with the klayout binary, the python module now sits inside 'pymod' 2018-06-19 00:50:27 +02:00
CONTRIB Updated CONTRIB file, preparations for RPM building. 2017-09-10 17:42:38 +00:00
COPYRIGHT Updated COPYRIGHT file with next version. 2018-05-03 21:49:59 +02:00
Changelog Fixed version in Changelog 2018-05-04 21:21:14 +02:00
Changelog.Debian Updated changelogs. 2018-05-03 07:13:57 +02:00
Jenkinsfile Generalized run_ut step in Jenkinsfile. 2018-06-24 12:30:17 +02:00
Jenkinsfile-publish-sources Fixed Jenkinsfile-publish-sources 2018-06-24 12:19:21 +02:00
LICENSE Initial commit 2017-02-12 12:54:21 +01:00
README.md Update README.md 2017-12-05 22:45:16 +01:00
build.sh WIP: unit tests for pykl, some build errors fixed. 2018-06-03 23:36:06 +02:00
build4mac.py adding symlinks to build4mac scripts 2018-03-16 17:01:56 -04:00
makeDMG4mac.py adding symlinks to build4mac scripts 2018-03-16 17:01:56 -04:00
version.sh Windows build fixed, version incremented to 0.25.3, updated changelog. 2018-05-02 21:47:30 +02:00

README.md

klayout

This repository will hold the main sources for the KLayout project.

Plugins can be included into the "plugins" directory from external sources.

For more details see http://www.klayout.org.

Building requirements

  • Qt 4.7 or later (4.6 with some restrictions) or Qt 5
  • gcc 4.6 or later or clang 3.8 or later

For more build instructions see http://www.klayout.de/build.html.

Build options

  • Ruby: with this option, Ruby scripts can be executed and developped within KLayout. Ruby support is detected automatically by the build script.
  • Python: with this option, Python scripts can be executed and developped within KLayout. Python support is detected automatically by the build script.
  • Qt binding: with this option, Qt objects are made available to Ruby and Python scripts. Qt bindings are enabled by default. Qt binding offers an option to create custom user interfaces from scripts and to interact with KLayout's main GUI. On the other hand, they provide a considerable overhead when building and running the application.
  • 64 bit coordinate support: with this option, the coordinate type used internally is extended to 64bit as compared to 32bit in the standard version. This will duplicate memory requirements for coordinate lists, but allow a larger design space. 64bit coordinate support is experimental and disabled by default.

Building instructions (Linux)

Plain building for Qt4

./build.sh 

Plain building for Qt5

./build.sh -qt5 

Building without Qt binding

./build.sh -without-qtbinding

Debug build

./build.sh -debug

Building with a particular Ruby version

./build.sh -ruby <path-to-ruby>

(path-to-ruby is the full path of the particular ruby interpreter)

Building with a particular Python version

./build.sh -python <path-to-python>

(path-to-python is the full path of the particular python interpreter)

Building with a particular Qt version

./build.sh -qmake <path-to-qmake>

(path-to-qmake is the full path of the particular qmake installation)

Building with 64bit coordinate support (experimental)

./build.sh -with-64bit-coord

Pass make options

./build.sh -j4 

(for running 4 jobs in parallel)

More options

For more options use

./build.sh -h

Running the Test Suite (Linux)

Go to the build directory (i.e. "bin-release") and enter

export TESTTMP=testtmp    # path to a directory that will hold temporary data (will be created)
export TESTSRC=..         # path to the source directory
./ut_runner

For more options use

./ut_runner -h