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.
Problems found with existing distfile for eagle:
distfiles/eagle-lin32-7.4.0.run
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.
are replaced with .include "../../devel/readline/buildlink3.mk", and
USE_GNU_READLINE are removed,
* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
are replaced with .include "../../mk/readline.buildlink3.mk".
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
was last updated.
Besides the upstream changes listed below, also add DESTDIR support
(which is enabled by better upstream support for it).
4. Version 7.5 Release Notes:
---------------------------------
Version 7.5 is the development branch. Version 7.5.0 is the same as
7.4.2, which is essentially the same as 7.3.123, plus some
documentation updates. Intended development is as follows:
1) Use a finely spaced grid for the database, but keep the concept
of "lambda" for layout. Keep backwards compatibility, and resolve
issues with layout that does not work well on the lambda grid.
Item #1 implemented in 7.5.1 by allowing a DRC "scalefactor" line,
which declares that all DRC rules are in units of (lambda /
scalefactor). Rules "in use" are scaled to lambda and rounded to
the nearest integer. The original value is retained, however, so
that any call to "scalegrid" will recompute the DRC distances based
on the current internal grid. Thus, we can define DRC rules in
fractional lambda and therefore match vendor DRC rule distances
while still maintaining magic's concept of "lambda". This means
that users working entirely within magic have scalable CMOS rules,
but if a "vendor cell" (3rd party GDS or CIF) is loaded, the DRC
rules will be correct with respect to it.
2) Create tile-based DRC functions that work like cifoutput: perform
tile operations, for which the resulting plane, instead of being
output as a file like CIF or GDS, simply becomes an error result
plane. This will become an extra built-in plane. Try to keep the
plane numbers down by removing the built-in routing planes when they
are not used.
Basically, this means that the top of the DRC section defines a set
of "templayer" blocks just like "cifinput" and "cifoutput" (but at the
same scaling as the layout (thus the main reason for item #1 above)),
where the templayer types can be used in the DRC section.
3) Add "cifoutput" operators as needed to form a complete DRC. Add DRC
rule types as needed to form a complete DRC (for example, it needs a
"copy" function that declares that the templayer itself represents the
error condition).
4. Version 7.4 Release Notes:
---------------------------------
Version 7.4 is the new stable distribution version of magic.
Apart from changes to the release notes, it is identical to
the last revision (123) of development version 7.3. Revisions
of 7.4 will be made as necessary to fix bugs in the code. All
new additions and major changes will be done to the new
development distribution, version 7.5. Therefore there will
not be a "What's new in 7.4" section, as there is not supposed
to be anything new in version 7.4.
5. Version 7.3 Release Notes:
---------------------------------
Magic release 7.3 incorporates a stacked contact model which is,
for the most part, backwardly compatible with Magic releases
7.2 and earlier. Information about this developmental release
can be found at:
http://opencircuitdesign.com/magic/magic7_3.html
What's new in 7.3:
------------------
Provided by Tim Edwards (MultiGiG, Inc.):
1) Stacked contact model allowing arbitrary stacking of
contact types.
2) A separate "undo/redo" method for network selection, to
remove the memory overhead associated with selecting and
unselecting large networks. Also removes some time overhead
as well, especially when unselecting networks.
3) Much improved "plot pnm" function.
4) Improved transistor and resistor extraction.
5) LEF format reader; improved LEF/DEF input/output handling
6) New style and colormap file formats
7) Vendor GDS read/write capability
8) "wire segment" drawing function
9) Handling of path records in CIF and GDS input
10) Handling of cell scaling in GDS input
11) Pi-network device extraction for resistors
12) Option to write contacts as cell arrays in GDS output
13) New "widespacing" and "maxwidth" DRC algorithms.
14) "polygon" command
15) New cifoutput operator "bloat-all"
16) Backing-store for 24-bit and OpenGL graphics
17) New "pick" tool for interactive selection move and copy
18) New interactive "wire" tool
19) Crosshair
20) New cifoutput operator "slots"
21) New fcntl-based file locking mechanism
22) "angstroms" units supported in cifinput/cifoutput
23) Non-Manhattan device extraction support
24) New "feedback" mechanism
25) Proper support for > 32 planes (up to 64)
26) Fixed array interaction CIF/GDS generation
27) Added executable "magicdnull" for streamlined batch-mode use
28) New method for crash backups, including restore with "magic -r"
29) A number of other technology file additions and enhancements
6. Version 7.2 Release Notes:
---------------------------------
Magic release 7.2 incorporates the capability to run magic from the Tcl
interpreter with graphics handled by Tk. Instructions for compiling
and installing this version are in README.Tcl. Information about
this release can be found at:
http://opencircuitdesign.com/magic/magic7_2.html
What's new in 7.2:
------------------
Provided by Tim Edwards (MultiGiG, Inc., and JHU Applied Physics Lab):
1) Tcl interpreter extension option
2) Cygwin compile option
3) Memory resources cleaned up
4) GUI interface to Tcl version of Magic
5) Readline update to version 4.3
6) OpenGL fixes and refinements
7) Nonmanhattan geometry fixes and extensions
8) Threaded graphics in non-Tcl environments
9) Inductance extraction
10) CIF and GDS input/output support for deep submicron technologies
11) Different internal and lambda grids, including automatic or
induced ("scalegrid" command) grid subdivision and expansion.
"snap" and "grid" functions and extensions aid layout when
lambda and internal units differ.
12) Removed commands "list", "listall", "parent", and "child",
replacing them with the more general-purpose "cellname"
and "instance" commands.
13) Added command "tech", and re-loadable technologies.
14) Revamped the "dstyle" files and updated the dstyle version
15) Added "element" types for layout annotation.
16) Extended extract section of techfile to include "device"
keyword and devices "mosfet", "bjt", "capacitor", and "resistor".
New model resistor and mosfet use width/length instead of area/
perimeter.
17) Added 3D rendering window invoked by command "specialopen wind3d",
for the Tcl version compiled with OpenGL graphics.
18) Added "height" keyword to tech file for height/thickness values
19) Added "windowname" command for managing multiple wrapper windows
under Tcl.
20) Added extraction extension for annular (ring) MOSFETs.
21) Added "widespacing" DRC rule.
22) Added GNU autoconf compile
23) New command "property" for setting key:value pair properties
in cell definitions that can be interpreted by other routines
(such as LEF/DEF).
24) General-purpose subcircuit method using the "port" command to
declare a cell to be a subcircuit and to mark the position and
orientation of connections into the subcell. This replaces a
method previously built into version 7.2 using a "subcircuit"
layer; that method is now considered obsolete.
25) LEF and DEF format readers, LEF format writer.
26) Improved techfile format with asterisk-notation and DRC
"surround", "overhang", and "rect_only" statements.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
and if that doesn't exist look for /usr/libexec/cpp0. While here,
use ${X11BASE}/include instead of /usr/X11R6/include.
Should fix recently noted bulk build problems on 1.6 systems.
points to the magic installation. This avoids possible conflicts with
some other UCB tools which use CAD_HOME. Noted in private email from
Daniel Senderowitz.
Magic is an interactive system for creating and modifying VLSI circuit
layouts. With Magic, you use a color graphics display and a mouse or
graphics tablet to design basic cells and to combine them
hierarchically into large structures. Magic is different from other
layout editors you may have used. The most important difference is
that Magic is more than just a color painting tool: it understands
quite a bit about the nature of circuits and uses this information to
provide you with additional operations. For example, Magic has
built-in knowledge of layout rules; as you are editing, it
continuously checks for rule violations. Magic also knows about
connectivity and transistors, and contains a built-in hierarchical
circuit extractor. Magic also has a plow operation that
you can use to stretch or compact cells. Lastly, Magic has routing
tools that you can use to make the global interconnections in your
circuits.
Magic is based on the Mead-Conway style of design. This means that it
uses simplified design rules and circuit structures. The
simplifications make it easier for you to design circuits and permit
Magic to provide powerful assistance that would not be possible
otherwise. However, they result in slightly less dense circuits than
you could get with more complex rules and structures. For example,
Magic permits only Manhattan designs (those whose edges are vertical
or horizontal).
