<@U020J2W6Q84> Is there any way to tell OpenLane2 ...
# openlane-2m
Matthew Guthaus
12/17/2024, 7:07 PM@donn Is there any way to tell OpenLane2 to NOT use local tools? This could be an issue that many people mess up. For example, I am going to teach a class where students will need a version of KLayout installed (the one in OL2 is not sufficient since it doesn't have Qt and therefore cannot use the Sky130 LVS menus). However, they will need to uninstall KLayout when they want to use OL2 otherwise they risk a problem. (I just ran into this yesterday with the 2.2.9 -> 2.3.0 update.)
Matthew Guthaus
12/17/2024, 7:13 PMOR:
Is there a way to issue a WARNING that it is using a local version? This should be the minimum...
Matthew Guthaus
12/17/2024, 7:24 PMIs it even true that it uses locally installed tools? I see this in the OL2 issues, and I had an issue with a locally installed klayout python module, but if I run Nix or Docker, it seems to have the non-locally installed version.
d
donn
12/17/2024, 8:51 PMTools, not Python modules. KLayout is its own nightmare.
donn
12/17/2024, 8:51 PMOh, you meant Qtbindings
m
Matthew Guthaus
12/17/2024, 9:17 PMYeah. The LVS scripts use it to open a menu:
https://github.com/efabless/sky130_klayout_pdk/blob/9e3b9c05e1a09f1376eaa232a9db73dcb48d747b/tech/sky130/pymacros/run_lvs.lym#L37
Matthew Guthaus
12/17/2024, 9:18 PMIt seems that it didn't even pick up a local tool though... I installed KLayout 0.29.10 and it still found 0.29.4 in Nix and Docker
d
donn
12/17/2024, 11:10 PMwell, it all depends on the values of
PATHPYTHONPATHdonn
12/17/2024, 11:11 PMA surefire no-nonsense workaround for this is just to use
openlane --dockerizeddonn
12/17/2024, 11:11 PM(Also I can just build KLayout with qtbindings if you want)
m
Matthew Guthaus
12/17/2024, 11:31 PMThe last would be ideal!
Ohhh, I see, the nix path is inserted before /usr/bin in my PATH, so it found the Nix copy rather than the local copy.
d
donn
12/18/2024, 9:02 PMOpenLane 2.3.1 should be pushed with a qtbinding-enabled version of KLayout.
However, that increases the build artifact size from ~70 MB to a whopping ~270 MB.
m
Matthew Guthaus
12/18/2024, 10:46 PMOof, yeah.
Matthew Guthaus
12/18/2024, 10:46 PMI see a use for it but understand if it doesn't deserve the image increase cost
d
donn
12/18/2024, 10:47 PMIt's already pushed. We may have to revisit this in the future but for now I want to make sure you have what you need.
20 Views