Install & Compatibility
Where this runs
tested against v0.2.14 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.910 runs
build_error
glibcpy 3.10–3.910 runs
installs and imports cleanly · install 24.0s · import 0.000s · 635MB
600MB installed
● package 600MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
LambdaPDK
✓ from lambdapdk import LambdaPDK
✗ from lambdapdk.pdk import sky130
This quickstart demonstrates how to initialize a `siliconcompiler` chip object and load the `lambdapdk` library to configure a Process Design Kit. `lambdapdk` is primarily used by passing its name as a string to `chip.load_pdk()`, allowing `siliconcompiler` to find and apply its definitions.
import siliconcompiler
import os
# Create a new chip object
chip = siliconcompiler.Chip("my_design")
# Load the lambdapdk library as the process design kit
# This automatically configures relevant paths and settings for the PDK
chip.load_pdk("lambdapdk")
# To confirm the PDK is loaded, you can check its name or other settings
print(f"PDK loaded: {chip.get('pdk', 'name')}")
# You would typically add source files, flow definition, etc., here
# Example:
# chip.input('adder.v', 'verilog')
# chip.set('design', 'adder')
# chip.set('flow', 'asicflow')
# chip.run()
Debug
Known issues
gotcha`lambdapdk` is designed to be used with the `siliconcompiler` EDA framework. Direct manipulation or importing of its internal modules (e.g., `lambdapdk.pdk.sky130`) outside of a `siliconcompiler` context might not be fully functional or could lead to unexpected behavior.fixAlways use `lambdapdk` in conjunction with `siliconcompiler.Chip` and its `load_pdk()` method for standard usage. Refer to `siliconcompiler` documentation for detailed PDK setup.
affects: All versions (0.x)
breakingMinor versions of `lambdapdk` (e.g., 0.2.x) can introduce internal API changes related to how PDK components are structured or how libraries are referenced (e.g., changes to memory model APIs, pin directions, foreign object positions). These changes might not be explicitly marked as breaking but can cause issues if `siliconcompiler` expects an older internal structure or if you rely on specific internal paths/settings.fixEnsure `lambdapdk` and `siliconcompiler` versions are compatible. If encountering unexpected errors after updating `lambdapdk`, check the `siliconcompiler` documentation and `lambdapdk` release notes for relevant internal API changes or configuration updates.
affects: >=0.2.0
gotchaWhile `lambdapdk` provides PDK *definitions* (paths, rules, etc.), it typically does not include all physical GDS, LEF, or Verilog library files. These often need to be pre-downloaded or made available on the system, with `SILICON_COMPILER_HOME` or other environment variables configured for `siliconcompiler` to locate them.fixConsult the `siliconcompiler` documentation and specific PDK setup guides (e.g., for Sky130, ASAP7) to ensure all required physical library files are present and correctly pointed to by `siliconcompiler`'s configuration or environment variables.
affects: All versions (0.x)
Upgrade
Version history
0.2.14latest on PyPI · released Jun 10, 2026
Audit
Dependencies
siliconcompilerrequiredlambdapdk is primarily used as a PDK provider for the siliconcompiler EDA framework; it defines PDKs that siliconcompiler then loads and utilizes.