Download And Build

All Downloads

Development Snapshot

A snapshot of the current development code base (last update 2010-03-09) can be obtained here:
klayout-r272.tar.gz.

Packaged Release For Windows

For the Windows platform, a zip archive is provided that contains all the required executables and DLL's. A description how to actually build KLayout on Windows using MinGW and CYGWIN can be found below.

Starting with version 0.15, an installer executable is provided as well. To install KLayout using the installer, download the executable and execute it. It will install the binaries at the target location, which can be selected in the installer user interface. In addition, it will create three KLayout shortcuts in the "Programs" section of the start menu. It will also register itself as handler for file types ".gds" and ".oas".

If the installer is executed from a normal user account, it will install itself for that user only. No particular rights are required in this case. If started with administrator rights, it will install itself for all users.

Building on MacOS

For MacOS 10.5.7, a universal binary is provided from the download link above. It requires a Qt 4.5.x installation. The Qt libraries can be obtained for example from http://www.qtsoftware.com/downloads/mac-os-cpp.

For building the executable on MacOS 10.5.7, the "mac-leopard-gcc-release" platform is provided. The build is based on the Xcode installation. This build script call was used successfully with Qt 4.5.2 from the Xcode package:

  ./build.sh -platform mac-leopard-gcc-release \
    -qtbin /Developer/Tools/Qt \
    -qtlib /usr/lib \
    -rblib /usr/lib/libruby.dylib \
    -rbinc /usr/lib/ruby/1.8/universal-darwin9.0

Building KLayout On Unix

System Requirements:

Linux system (tested on Ubuntu 7.10, 8.04LTS, RHE 3)
on Linux: gcc Version 3.2 or later (tested with 3.4.5, 4.3.2). Solaris is no longer supported.
Qt Version 4.2.x or later (tested with 4.2.3, 4.4.3).

To build, the simplest way is to use the build.sh wrapper script provided. Unpack the tarkit, change to the directory created and type

./build.sh

If the script complains about missing tools are libraries, the Qt installation needs to be specified. There are basically two ways: either a Qt package was configured or installed using the environment provided by TrollTech, or the system provides a Qt4 installtion itself.

In the first case, the actual Qt installation path can be specified with the -qt option: i.e.

./build.sh -qt ~/qt

will locate the Qt include files in ~/qt/include, the Qt library in ~/qt/lib. The installation path is the prefix that was specified on Qt's configure command line.

On LSB (Linux Standard Base) systems, the Qt4 library can be optionally installed. It is common to have different installation directories for include and library files. On Ubuntu 6.10 with Qt4 for example, the libraries are located in "/usr/lib", the development tools like "uic" are installed in "/usr/bin" and the include files reside in "/usr/include/qt4". In this case, use:

./build.sh -qtbin /usr/bin -qtlib /usr/lib -qtinc /usr/include/qt4

Since the above settings are the default, this is equivalent to specifying nothing as shown above.

The build script does not determine the platform to build upon. By default, 32 bit Linux and "gcc" is configured as the build platform. To build for an other platform, use

./build.sh -platform <platform>

The platforms and build variants available are listed with

./build.sh -help

The build script will create the final executable in

./bin.<platform>/klayout

To integrate other build variants, a new file can be created in the "config" subdirectory. This is a partial Makefile that defined the variables specific for a certain build.

To enable Ruby script automation capabilities (RBA), the Ruby library and path to the Ruby headers must be specified for the build script:

build.sh -rblib <ruby library path> -rbinc <ruby headers location>

For example:

build.sh -rblib /usr/lib/libruby1.8.so -rbinc /usr/lib/ruby/1.8/i486-linux

For more details about RBA, see RBA introduction.

Building KLayout On Windows with CYGWIN/MinGW

A build setup is provided for MinGW with the gcc using CYGWIN as the build environment. The procedure has been tested with MinGW 5.1.3 and Qt 4.3.2. Other combinations may not work as expected.

The build script can be used on CYGWIN for example to build an executable, provided, Qt4, MinGW and gcc is installed. gcc version should be 3.2.3 at least, the Qt version should be 4.2.x at least. A zlib for MINGW must be installed.

Two build variants are provided: "console" and "window" application. The console application comes with a console window that is used to print diagnostic messages on.

The build step itself is pretty much the same than on Unix. Use the shell provided by CYGWIN (bash console or xterm with the X11 emulator) to start the build script. Unlike on UNIX, the build process produces a main executable ("klayout.exe") and a body DLL ("klayout.dll").

Note: for the Qt installation path (parameters -qt, -qtlib and others), the CYGWIN path (i.e. "/cygdrive/c/Qt/4.3.2") must be specified for the build script.

For the installation, copy the main executable, the body DLL and the Qt and MinGW DLL's into an installation directory and start the tool from there.