./cad/gdsreader, GDS-II stream file to Postscript and HP/GL converter

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 0.3.2, Package name: gdsreader-0.3.2, Maintainer: pkgsrc-users

GDSreader - simple Calma (GDSii) parser/printer tool.

This software has as target the printing/plotting/displaying of Calma (GDSii)
files without using true layout editors. I had once to visualize an unknown
Calma file and customizing LEdit or Magic (the two layout editors I had access
to) was so difficult that I decided to write this program.

Current status:
- gdsreader is in an alpha stage and you should not expect too much from it;
- the Calma files are almost completely parsed (had no layout example that
makes use of BOX/NODE elements);
- given a Calma structure name, a PostScript file and a HPGL/2 file are
generated. The way each layer is handled is controlled by an ASCII
configuration file. The properties that can be set are color, fill (only
solid is supported), hatch (simple or cross, the angle and spacing are user
customizable too).

In order to produce an useful PostScript output, you need to write a
configuration file (default is .layers.config). The one you'll find with the
distribution is suitable for the Calma example test.gds (an actual Bandgap

Required to build:

Master sites:

SHA1: 200fe93b9c44639acb9b5da94c9f0061c49bd3b0
RMD160: da990de44a70c8cc1cc1df6bcfdd6d457a3efa20
Filesize: 80.712 KB

Version history: (Expand)

CVS history: (Expand)

   2019-06-08 13:04:30 by Roland Illig | Files touched by this commit (43)
Log message:
cad/*: let pkglint fix indentation, variable alignment, and LOCALBASE

pkglint -Wall -r -F cad

Manually fixed the indentation in cad/ghdl/Makefile because SITES.* was
(by the current definition) not long enough to count as an outlier line,
and because of this, all other lines were aligned to that line.
   2015-11-03 01:21:20 by Alistair G. Crooks | Files touched by this commit (58)
Log message:
Add SHA512 digests for distfiles for cad category

Problems found with existing distfile for eagle:
No changes made to eagle/distinfo file.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2014-10-22 00:38:44 by Makoto Fujiwara | Files touched by this commit (4) | Package updated
Log message:
   - Convert MASTER_SITES to distcache of FreeBSD
   - Delete patch-aa, taking care by Makefile of pkgsrc side
   - Update GDSreader 0.3 to 0.3.2
New feature for gdsreader-0.3.2

  Generation of POVRAY scene files.

Quick Overview:

GDS2, (or "Calma"), files contain 2D shape data, and each shape has
a specific layer number, (gdsno), and a datatype number.  To  make
any sort of 3D model, these two integer numbers must be  "mapped"
to a corresponding thickness and depth parameter, and  also to a
color specification.   This  is handled by the user-created
"layers.config" file.  A  layers.config file needs to be made for
each technology you wish to convert.  A process which differs only
in the number of metal layers used is considered a different
technology.  The layers.config file is also used in the generation
of postscript and HPGL output, so several of the parameters in
a layers.config file do not necessarily apply to POVRAY output.

.. (more to read) share/examples/gdsreader/README.povray
   2012-10-08 15:25:17 by Aleksej Saushev | Files touched by this commit (62)
Log message:
Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.
   2009-06-14 19:35:57 by Joerg Sonnenberger | Files touched by this commit (52)
Log message:
Remove @dirrm entries from PLISTs
   2008-07-14 14:56:20 by Joerg Sonnenberger | Files touched by this commit (563)
Log message:
Mark as destdir ready.
   2008-06-20 03:09:45 by Joerg Sonnenberger | Files touched by this commit (993)
Log message:
Add DESTDIR support.
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't