MKPR

NAME
SYNOPSIS
PARAMETERS
OPTIONS
DESCRIPTION
LIMITATIONS
EXAMPLES
AUTHORS
FILES
SEE ALSO
DIAGNOSTICS

NAME

mkpr - make a project

SYNOPSIS

mkpr [-p process] [-l lambda] [-u project] project

PARAMETERS

project

Absolute or relative path of the project to be created.

OPTIONS

-p process

Create project for the specified process. process can be a process name, a process number or a process directory.

-l lambda

Use the specified lambda value (in microns) for the project.

-u project

Use existing project (path) for parameter defaults.

DESCRIPTION

Mkpr creates a project (for the latest release) with the specified name. The argument may contain /'s, in which case the first part (up to the last /) has to be a legal UNIX path to a directory in which the new project directory will be created. Mkpr requires write permission in the parent directory.

Default, mkpr tries to use the information of the current project (if existing). Use option -u, to use a specific project instead.

To connect the project to a process, mkpr first tries to use the process that is specified using the option -p, second the value of an existing current project. Next, mkpr tries to use the environment variable ICDPROCESS (if defined). Otherwise, the user has to interactively specify the process.

To define a lambda value (the smallest grid for layout design) for the project, mkpr first tries to use the value that is specified using the option -l, second the value of an existing current project. Next, mkpr tries to read the value from a file `default_lambda' that is present in the process directory. Otherwise, the user has to interactively specify the value for lambda.

Mkpr creates standard entries in the project directory, that is, view directories with empty celllists, a file ".dmrc" and a file "projlist". The entry ".dmrc" contains process information such as the process id and the value for lambda. The entry "projlist" is intended to contain a list of paths to projects that may be used as libraries for the design that will be created in the new project.

LIMITATIONS

Mkpr does not use the environment variable CWD.

EXAMPLES

$ mkpr my_project
$ mkpr -l 0.1 my_project2
$ mkpr -p scmos_n -l 0.1 ../../projects/new_project
$ mkpr -p /usr/cacd/lib/process/scmos_n -l 0.1 other_project
$ mkpr -u other_project other_project2

AUTHORS

P. van der Wolf, A.J. van Genderen, S. de Graaf

FILES

ICDPATH/share/lib/process/processlist

(input file)

project/.dmrc

(output file)

project/projlist

(output file)

project/view/celllist

(output file)

project/view/impcelllist

(output file)

ICDPATH/share/lib/process/name/default_lambda

(opt. input file)

ICDPROCESS/default_lambda

(opt. input file)

SEE ALSO

addproj(1ICD), getproc(1ICD), rmpr(1ICD).

DIAGNOSTICS

Upon successful completion mkpr returns exit code 0. Otherwise, a diagnostic is printed and 1 is returned.