Linuxpackages are signed with the GPG public key (Matthias Koefferlein).
Windows packages are signed with a code signing certificate (issued by Certum) as: "Open Source Developer, Matthias Koefferlein".
For the Windows platform, a self-extracting installer binary is available.To install KLayout using the installer, download the executable and run 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" and other related formats.
If the installer is executed from a normal user account, it will install itself for that user only. No particular rights arerequired in this case. If started with administrator rights, it will install itself for all users.
Alternatively, a zip archive is provided that contains all the required executables and DLLs. It is possible to run KLayout directly from these files after extracting the archive.The KLayout executable is "klayout_app.exe".Using the .zip archive is the recommended way to try KLayout without contaminating the system.
For CentOS and OpenSuSE systems, RPM packages (.rpm) are provided on the download page. For Ubuntu, Debianpackages (.deb) are supplied. Only 64bit systems are supported, because 32bit is about to vanish now.All packages are signed with the GPG public key (Matthias Koefferlein).
The "klayout-bits4msvc2017" project ( _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.
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:
MSYS2 has three target systems: "mingw64" as a build environment for 64bit applications, "mingw32" for 32bit applications and "msys2" for build runtime. A variety of packages need to installed using the "pacman" package manager or MSYS2.To install these packages, open a MSYS2 shell and install the packages with pacman:
After the build finished, you will find the binary in "bin-release". To run it, stay in the MINGW 64bit shell.With Python3 you will initially see an error indicating that Python cannot find the encoding librariy.This is because the Python path is not set yet.You can do so by setting the "KLAYOUT_PYTHONPATH" environment variable. However it is easierto create a file KLayout reads to set the Python path:
A script is provided that integrates the build and packaging steps and generates the installer using the Nullsoft install system (NSIS). This script is "deploy-win-mingw.sh" from the "scripts" directory. It requires MSYS2, the packages mentioned above and the NSIS installer system ( -
dev.github.io/).
3a8082e126