Matthias
Hi Jim,
you can use master or any other branch, but without warranty.
The usual approach (and the one favoured by GitHub) is: features are developed in branches. When they are considered stable enough they are integrated into the master (pull request). Hence the master is kind of "latest greatest", but with a certain risk of being spoiled. There are also forks from other user with their own masters and branches. Don't confuse them with the ones from the KLayout project.
But eventually, when the master is considered to have a sufficient quality, a release is made by creating a release tag (https://github.com/KLayout/klayout/releases). A release is a snapshot which is then turned into Windows binaries, Linux packages, PyPI wheels etc. This this is a lengthy process and I don't want to do this too often.
Matthias
About
- Username
- Matthias
- Joined
- Visits
- 1,515
- Last Active
- Roles
- Member
Comments
-
Hi Ghis, I have updated the build information accordingly. Thank you for that hint. Best regards, Matthias
-
Hi Brendan, that is a useful remark, thank you. I was thinking of simply transforming the layout, not the images and rulers. That is possible of course too. I was assuming that one use case is to transform a layout to match it to an image .. Bes…
-
Hi Brendan, I have been asked for the feature some times already. It's always somewhat difficult to explain. Obviously you are right - it's somewhat too elaborate for simple use cases. It should not be a big issue to implement some more guidance a…
-
Hi, that's easy to implement and therefore already there :-) Actually it is possible to transform each layer or layer group individually and in particular to transform one layout relative to another if multiple layouts are loaded. The feature is …
-
Hi Jo, Thanks, that was very helpful! I'll provide a new version of the build script that uses the system zlib as far as possible. Best regards, Matthias
-
Hallo all, I similar issue has been reported here: http://klayout.de/forum/comments.php?DiscussionID=104&page=1 Apparently it helps to build KLayout with the system zlib. See under the link above for a description how to do so. Matthias
-
Hi Jo, at least that is a workaround. I am still suspecting that it's the zlib which causes the problems, although I don't see any problems with the systems I have had so far. If by chance you find the time to check if it works with the system zl…
-
You're welcome :-) I admit it's more tedious than it should be. I'll try to provide a better solution in the next release, like the one you already mentioned. BTW: if you need performance, the script can be set up somewhat more efficient by not me…
-
Hi Acku, there is nothing special with the properties. All you need to do is to create a mapping for the property id's and apply the new id's. Below is the new script. Best regards, Matthias # Merge two layouts # This script merges two layouts…
-
Hi Acku, Being able to load a file into an existing layout is actually a nice suggestion! Right now that use case is not supported and seeing those error message would not surprise me. I admit such a feature would be quite useful. I'll try to cons…
-
Hi Acku, merging of layouts is not the strength of RBA but it's possible (although probably slower than the native functionality). Here is a sample script that takes two layouts (a.gds and b.gds) and merges them. It illustrates how to solve the pr…
-
Hi Jo, I had a report of a similar issue before: [http://klayout.de/forum/comments.php?DiscussionID=98&page=1#Item_9]. That case apparently was related to the native file dialog, which was GTk. My suggestion was to try with a different style, …
-
The link is working again.
-
Hi Jimmy, that is very good input. Thanks for the analysis. In fact, you're right. There is something different with respect to the zlib. For 0.21 I was including a copy of the code (zlib 1.2.5). This way it was much more convenient to build on Wi…
-
Hi Jimmy, One thing that has changed is the handling of UTF8 encoding locales. But that should make it better, not worse. In the case of GDS files, the reader uses the zlib which I assume is active in your case. I am not aware that zlib is encoding…
-
Hi Jimmy, that is really weired. There should not be any difference in GDS files saved by this or other versions. The error message indicates that there is something very basic wrong, like something with the fopen function. Are you able to open t…
-
Hi Jimmy, the QFrame constructor mentioned in the error message is a special one which is only provided if the code is compiled with -DQT3_SUPPORT (which is the case) and the Qt library is built with Qt3 support. Usually that is the case but depend…
-
Hi Jimmy, I am not quite familiar with MacOS builds (I don't make the MacOS binaries myself), but I found one post which describes a similar problem here: http://www.cocoaforge.com/viewtopic.php?f=6&t=21261 Frankly I don't quite understand wh…
-
Hallo, you're right, the two tools serve the same purpose. However, there is a important difference: The XOR tool performs a comparison of the merged polygons as seen from the top cell. This basically verifies the equivalence of two layouts in th…
-
Hi Werd, I admit, I am somewhat helpless now. I am quite sure (from your stack trace) that the problem is related to QGtkStyle, but I can't reproduce it, even after explicitly enabling GTK style. What puzzles me is that this style is supposed to w…
-
Hi, thank you for the stack trace. It indicates that the problem happens inside GTK's file dialog and does not seem to be related to Qt or KLayout at the first glance. Google gave me some hint that libxml2 might be the problem (https://bugs.launch…
-
Hi, you can create a stack trace with the GNU debugger (gdb) for example. It usually comes with the gcc package, so I assume you have it already. Instead of starting KLayout directly, enter gdb cd {where klayout resides}gdb ./klayout on the gdb …
-
Hi, the logs look OK as well as the package list. I assume that gcc 4.4.0 is in your path. The Qt package is somewhat outdated - the oldest one I am testing on is 4.2.3. Although not a lot Qt-related code has changed to 0.21, I had issues with some…
-
Hi Ray, meanwhile I made some experiments with TrueView myself. You're right that it's somewhat more picky than other viewers. Since it delivers some meaningful error messages I was able to change the DXF writer accordingly. Right now, I don't have…
-
Hi Ray, line 22 is always the first entry in the layer table. More precisely that is the layer name (as the message says). When I export GDS (or another format using numbers for layers) to DXF I create layer names of the form LxDy where x is the l…
-
Hi Ray, I found the bug in the "save visible only" feature. It also applied to CIF writing. Thanks for reporting that issue. I'll put the fix in the next minor release (0.21.2). I have not installed TrueView yet to track down the reading…
-
Hi, Sorry for not mentioning that here. Yes it is. I changed to code above so it is a full Ruby module. Copy the code into some file, i.e. "multiclip.rbm" and run KLayout (version 0.21.1) like this: klayout -rm multiclip.rbm ... If you …
-
Hallo, basically you can use KLayout non-interactively. If you run KLayout this way: klayout -e -z -r script.rb ... you can run the script without bringing up a GUI. You can pass arguments to the script by defining Ruby variables, i.e. klayout …
-
Hi Kalle, you're welcome :-) Actually you have not been the only one mentioning that issue. Since MinGW is well supported as a build platform at least on 32bit it was not a big deal to create the package. I'll maintain this build for the next vers…
-
Hi Kalle, I provided a new binary package made with MinGW which is very similar to the ones I provided before. Lacking a W2K installation, I cannot check the package myself but I am very confident that this solves that issue. The package is availa…