KLayout Main Sources
Go to file
Thomas Ferreira de Lima 1bba72e45b
Adding documentation regarding manylinux, CI, and PyPI wheels
2018-12-20 16:10:55 -05:00
ci-scripts Adding documentation regarding manylinux, CI, and PyPI wheels 2018-12-20 16:10:55 -05:00
etc Updated CONTRIB file, preparations for RPM building. 2017-09-10 17:42:38 +00:00
macbuild os.makedirs has no exist_ok in python2 2018-10-05 09:42:42 -04:00
scripts Fixed RPM spec file 2018-10-22 22:45:26 +02:00
src fixing pya module. adding tests 2018-12-20 16:10:55 -05:00
testdata Fixed #198 (DXF contour stitching renders fuzzy polygons) 2018-11-22 22:19:46 +01:00
.gitignore Updated .gitignore. 2018-09-09 18:31:27 +02:00
.travis.yml Not testing cp27-cp27m in travis's host (incompatible). 2018-12-20 16:10:55 -05:00
CONTRIB Updated CONTRIB file, preparations for RPM building. 2017-09-10 17:42:38 +00:00
COPYRIGHT Updated version and changelog. 2018-07-11 00:40:58 +02:00
Changelog Fixed typo in Changelog 2018-10-20 09:56:45 +02:00
Changelog.Debian Merge branch 'pymod-test' of https://github.com/lightwave-lab/klayout into lightwave-lab-pymod-test 2018-09-30 23:19:37 +02:00
Jenkinsfile Generalized run_ut step in Jenkinsfile. 2018-06-24 12:30:17 +02:00
Jenkinsfile-publish-doc Added doc publishing step. 2018-06-24 18:24:13 +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
MANIFEST.in bugfix for setup.py sdist 2018-10-09 17:31:53 -04:00
Makefile fixing ut_runner by adding DYLD_LIBRARY_PATH to env varas 2018-10-05 10:23:24 -04:00
README.md Windows build script and setup.py for Anaconda (install needs testing). 2018-09-13 01:11:18 +02:00
build.bat Fixed build.bat - wasn't properly exiting and did not really perform a build without install (the latter is important for producing the unit test runner binary 2018-09-27 21:58:16 +02:00
build.sh More reliable detection of extension suffix for Python 2.x 2018-07-16 00:56:12 +02:00
build4mac.py adding symlinks to build4mac scripts 2018-03-16 17:01:56 -04:00
dropbox-deployment.yml pushing wheel to dropbox 2018-07-16 22:26:17 -04:00
makeDMG4mac.py adding symlinks to build4mac scripts 2018-03-16 17:01:56 -04:00
setup.py changing version to 0.26.0.dev10 2018-12-20 16:10:55 -05:00
test-pylib-script.py Manual merge of remaining files from lightwave-lab:pymod-test to pymod 2018-10-02 22:41:08 +02:00
travis-build.sh improving build process. tentative fix to python3 osx10.11 2018-10-05 09:42:42 -04:00
version.sh Preparations for 0.25.5 release (updated Changelogs, version) 2018-09-19 22:05:39 +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

Building on Linux:

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

Building on Windows with MSYS2:

  • MSYS2 with gcc, Qt4 or 5, zlib, ruby and python packages installed

Building on Windows with MSVC 2017:

  • MSVC 2017
  • Build requisites from klayout-kit

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

Build instructions (Windows, MSYS2)

From the MSYS2 MinGW bash (32 bit or 64 bit) use the same commands as for Linux to build the binaries.

Build instructions (Windows, MSVC 2017)

The combination supported and tested was Qt 5.11/MSVC 2017 64bit. It's sufficient to install the build tools from MSVC's community edition.

A build script similar to build.sh is provided for Windows (build.bat).

For details about this build script use

build.bat -h

For MSVC builds a number of third party libraries are required:

  • Ruby
  • Python
  • zlib
  • expat
  • curl
  • pthread-win

The "klayout-bits4msvc2017" project (https://github.com/klayoutmatthias/klayout_bits4msvc2017) targets towards providing a binary distribution for this purpose. See the release notes there for download links. Download the .zip archive from there and unpack it to some folder, e.g. "c:\klayout-bits".

The build script needs the path to this package. "qmake" and (for obtaining the build version) "git" should be in the path. If qmake is not in the path, you can use "build.bat -qmake ..." to specify qmake's path.

Here is an example for the build.bat call:

build.bat -bits c:\klayout-bits

The 3rd party bits kit can also be used to build the Python standalone package on setuptools. Specify the full path to the 3rd party package up to the compiler and architecture. On 64bit with the bits package installed in "c:\klayout-bits" the build call is this:

set KLAYOUT_BITS=c:\klayout-bits\msvc2017\x64
python setup.py build