have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
redefines about which buildlink.mk files would care is BUILDLINK_X11_DIR,
which points to the location of the X11R6 hierarchy used during building.
If x11.buildlink.mk isn't included, then BUILDLINK_X11_DIR defaults to
${X11BASE} (set in bsd.pkg.mk), so its value is always safe to use. Remove
the ifdefs surrounding the use of BUILDLINK_X11_DIR in tk/buildlink.mk and
revert changes to move x11.buildlink.mk before the other buildlink.mk files.
use X11_BUILDLINK_MK as a test value. Generally just reordering the
inclusions so that x11.buildlink.mk comes before the other buildlink.mk
files will make everthing work.
"libtcmgui" instead of "libgui". emulators/gpsim installs a libgui
which causes problems. There may be conflicts with the other libs
(libglobal, libtable, etc). To be safe, rename them all similarly.
Get rid of the terrible configure script. It saved a few patches, but
isn't worth the ugliness.
TCM is a collection of graphical editors for different software
specification methods. It contains generic editors (for generic
diagrams, tables and trees), editors for Structured Analysis
(entity-relationship diagrams, data and event flow diagrams,
state-transition diagrams, function refinement trees etc.) and editors
for UML (static-structure diagrams, use-case diagrams, activity
diagrams etc.).
TCM supports constraint checking for single documents (e.g. name
duplication and cycles in is-a relationships). TCM distinguishes
built-in constraints (of which a violation cannot even be attempted)
from immediate constraints (of which an attempted violation is
immediately prevented) and soft constraints (against which the editor
provides a warning when it checks the drawing). TCM is planned to
support hierarchic graphs, so that it can handle, for example,
hierarchic statecharts. Features to be added later include constraint
checking across documents and executable models.
In addition to the TCM file format, TCM outputs Plain PostScript,
Encapsulated PostScript, PNG and the XFig file format. The TCM file
format is simple to read and parse so other forms of output can be
generated easily.
