.ig Copyright (C) 1993,1994 by the author(s). This software is published in the hope that it will be useful, but WITHOUT ANY WARRANTY for any part of this software to work correctly or as described in the manuals. See the ShapeTools Public License for details. Permission is granted to use, copy, modify, or distribute any part of this software but only under the conditions described in the ShapeTools Public License. A copy of this license is supposed to have been given to you along with ShapeTools in a file named LICENSE. Among other things, this copyright notice and the Public License must be preserved on all copies. Author: Andreas Lampen (Andreas.Lampen@cs.tu-berlin.de) $Header: shape_depend.1[6.0] Fri Jun 25 17:01:44 1993 andy@cs.tu-berlin.de frozen $ .. .TH "SHAPE_DEPEND" 1 "" \n(dy.\n(mo.\n(yr .SH NAME shape_depend \- shapeTools RMS determine source-include dependencies .SH SYNOPSIS \fBshape depend [VERSIONS=] [variants]\fP .sp .SH DESCRIPTION The shape release management system requires for each node system a file named \fIDependencies\fP, listing the source\-derived dependencies of the node components. \fIshape depend\fP automatically determines these dependencies and creates an appropriate Dependencies file. The dependencies have the form of regular Makefile target\-dependents lines without associated build action. .PP .in +1c .ll -1c \fBNote:\fP shape depend only works for development of C programs. It additionally requires a C compiler supporting the \fI-M\fP (generate Makefile dependencies) option. If this is not the case in your development project, you must either rewrite the action associated with the depend target (in $(SHAPELIBPATH)/stdtargets) or maintain the Dependencies files manually. .in -1c .ll +1c .PP The \fIVERSIONS\fP macro defines the version selection rule to be used. Default is \fImost_recent\fP. See shape_stdrul(7) or the $(SHAPELIBPATH)/stdrules file for other possible settings. You may also use self defined version selection rules as VERSIONS rule. .PP If your development environment contains variant definitions, in especially variant definitions that modify the list of source components to be used during a build operation, you may also need to specify one or more \fIvariants\fP to be set. The project wide variant raster is defined in $(SHAPELIBPATH)/stdvar. Check this file and the default variant settings in your Shapefile before invoking shape depend. .SH INCONVENIENCES Regeneration of the Dependencies file due to structural changes of the node system has to be triggered manually. Shape RMS doesn't recognize such changes. .PP Variant specific Dependencies files (necessary when simultaneousky developing structurally different variants) are not supported. In this case you have to run shape depend prior to each build action. .SH FILES $(SHAPELIBPATH)/stdrules .br $(SHAPELIBPATH)/stdtargets .br $(SHAPELIBPATH)/stdvar .SH SEE ALSO shape_RMS (1)