@Matthias , sorry!
I have comletly confused you. I meant DEF import, not export!
I'll try to explain it again:
When I run klayout whith .lyt and GDS file as parameter (see first scrinshot below), I see, that technology parameters loaded successfull…
There is really full path to klayoutrc in the warning:
"Warning: Could not create backup file: unable to rename original file '/proj/memcom/memcom_tools/KLayout/klayoutrc' to backup file"
And KLAYOUT_BASE_PATH variable set corr…
@Matthias, thank you for reply!
klayoutrc file is not moved! KLayout is not enable to rename it and it returns the corresponding warning:
"Warning: Could not create backup file: unable to rename original file '/klayoutrc' to backup file"
@Matthias OK, I got it. But in this case the checkbox description "Coordinates in database units" is quite confusing because there is no understanding what database is meant by. In my case I decided that after this checkbox is enabled I'll…
Yessss! Finally I got Klayout compiled successfully with support of Ruby and Python.
Klayout compilation failed with Ruby 2.3.0 that is compiled with static libraries, even if I fixed your build.sh.
I used "--enable-shared" op…
Of course, I can do that, but I'm not very familiar with compilation process.
Please, explain me how should I "build KLayout in debug mode" and how to "run it within gdb"?
Is "gdb backtrace" you need just …
I decided to install Klayout with Ruby and Python support and installed the latest tools versions: Ruby-2.3.0 and Python-3.5.1.
They are installed successfully without errors.
Then I run klayout compilation like ./build.sh -qt /tools/Q…
I use Qt 4.8.6 too. I installed gcc 4.8.4 (the same as you use) and compiled klayout with it.
Klayout behavior didn't change. Corruptions with "Segmentation fault" occurs randomly during ruler coordinates edition.
I checked that my GCC is: g++ (GCC) 4.1.2 20080704 (Red Hat 4.1.2-50)
I was going to prepare a testcase for you (small gds and particular ruler coordinates), but found that "segmentation fault" occurs not every time I change…
You are right, I have Python 2.4.3 and ruby 1.8.5 and both these versions are not supported.
I was able to compile klayout only with -nopython and -noruby options.
Thank you very much for your help.
Your klayout is the best and very h…
you wrote : I guess you mean "Import LEF", not "File/Open LEF", right?
And this became a key to all my issues with LEF.
The problem was that till last time we used 0.21.13 version of KLayout which I installed about 3 …
yes, I use the latest version.
I can print testcase right here:
--- BEGIN testcase.lef ----
VERSION 5.6 ;
BUSBITCHARS "" ;
DIVIDERCHAR "/" ;
CLASS BLOCK ;
ORIGIN 0 0 ;
FOREIGN testcase 0 0 ;
1) Yes, I specify .lyp file in "Setup/Layer Properties" dialog in "Use default layer properties file" section.
2) "Automatically add other layers" option is enabled.
Looks like this option works partly. It works correct…
Looks like the problem is in layers property file loading in the latest version of KLayout comparing to 0.19.3 version. The latest version loads default layers with old LEF.rb, even if $lvlyp is defined, or do not load any with new LEF.rbm.
And one more issue :)
If I use workable old version of LEF.rb (by copying it in $KLAYOUT_PATH), the latest KLayout ignores some other ruby modules (like tech_manager.rbm) and do not open GDS from command line. :(
-- Eugene Stolbikov
No, there are no any error messages.
I see just cell name in Cell window.
Here is a small LEF example that looks OK in my old LEF.rb and doesn't in new LEF.rbm:
VERSION 5.5 …
yes, you understand me correctly and ways you showed are interesting.
But I'm not a good Ruby programmer :) and there are a lot of different log files and databases from which I take coordinates. It's even can be a coordinates from intera…
thank you for the respose.
I tried tech_manager module you had recommended me.
It works, but it is not "interactive". After technology selection from menu it just write new settings in your local configuration file and requires …