# 623 ; The PROJECT group is the main group of all projects. This describes the
# basic information on the project and is used by RVDEBUG to handle project
# control. Most of the fields in this group are pre-filled in and should
# not be modified.
[TEMPLATE=&PROJECT]     \\ Defines base project information
# 570 ; The specific_device field allows selective project binding. This
# means that the project will only bind to the named devices if
# any. If none specified, the project will bind to all devices 
# of the processor type the project is for. The name(s) given
# must match the device_names from the JTAG-file. You can specify
# multiple names, and each will be tested. This is useful with
# multi-processor systems where each device has a different
# program to load.
specific_device=LS      \\ Name of specific device(s) to bind to
# 497 ; 
description=S           \\ Description of this project
# 536 ; 
processor_=K(470*R1X,C54*X,C2xx,C5x)\\ Processor project builds for
# 510 ; 
type_=K(Simple,Makefile,Container)1 \\ Type of project this is
# 477 ; The author field is filled in with the original author of this project.
# This allows for locking by author (only the author can modify it).
author_=S               \\ Name of author of this project
# 667 ; Locking allows the project itself to be controlled. A version lock means
# that the version/source control used for source files will be used for
# project files as well. The project will be checked into the source
# control system by RVDEBUG. Attempts to modify it will automatically
# check the files out. Checking the file in will also allow stamping
# the sources as well. A user lock means that only the author can 
# modify the file (using RVDEBUG).
lock=K(unlocked,versioned,user) \\ Type of lock model for project updates\K\
                        No lock control,Version/Source Control locked,\
                        Only author can change
# 558 ; The base directory of the project is used to allow all sources and
# build files to be relative to the base (if within it or a sub-directory).
# This way, a copy of the project can be made that is moved to a new base
# and so local modifications can be made. If the path is left empty,
# the base-directory will be the directory of this file.
base_directory=D"<use path of project file>" \\ Base directory of project
# 590 ; The tool-directory field is one or more paths to find tools to run. These
# will be added to the path environment variable prior to running any
# tools.
tool_directory=D        \\ Location for all tools (by default).
# 476 ; The tool-envvar fields are used to define environment variables that
# should be set prior to running any tools.
tool_envvar=LS          \\ Environment variables needed by tools
# 725 ; Source search paths allows setting the list of directories to
# find sources. This is only needed when the compiler/assembler
# does not pass the source paths through to the debugger. You
# know you need this when the debugger cannot find the source
# files automatically.
source_search=LD        \\ Source search paths for debugging
# 560 ; Source mapping paths allows setting the list of directories to
# find sources when projects are moved from their original location.
# This is only needed when the compiler/assembler
# does not pass the current source paths through to the debugger.
source_mapping=LL       \\ Source mapping paths for debugging
# 589 ; Command Open/Close allows you to specify a set of RVDEBUG 
# commands to run when the project is opened or closed. This
# may be any command including loading a command include file.
# Common examples for open are "reload" to immediately load 
# the file and also breakpoint setup and macro setup. Common
# examples for close are "del macro" to delete macros created
# for a project.
{.Command_Open_Close
  # 724 ; 
  open=LS               \\ RVDEBUG commands to run on project open
  # 496 ; 
  close=LS              \\ RVDEBUG commands to run on project close
}
# 687 ; The modification history is built automatically each time the project
# is edited. It contains the user, date, and type of modification that
# took place.
{Modification_History   \\ History of changes
  # 537 ; 
  user_=S               \\ Name of person changing
  # 440 ; 
  date_=S               \\ Date changed
  # 499 ; 
  type=K(created,added_to,deleted_from,other)0
  # 461 ; 
  description=S         \\ Description of changes
}
[INCLUDE] ?prj_set.stp
# 674 ;
[TEMPLATE=MAKEFILE]
# 396 ;
makefile=F              \\ Location of Makefile to build
# 653 ;
application=F           \\ Name of target application to build
# 567 ;
arguments=S             \\ Arguments to pass to make or command
# 690 ;
cwd=K(local,same_makefile,same_application) \
                        \\ Defines working directory when running make\K\
                        In project base directory,Same as makefile,\
                        Same as application executable file
# 580 ; Command allows overriding the make command by using your own.
# Note that if not supplied but one is supplied in the Tool
# Settings for this processor, that will be used (called Make_cmd).
# Like Make_cmd in Tool Settings, this is a command string that
# can include controls that RVDEBUG will expand (see below). Unlike 
# make_cmd, nothing will be added to this command (it can be 
# whatever you like). The control chars start with a $ and are 
# followed by a letter. The allowed control chars are: $f is the
# makefile name, $a are the args for the command, $e is either 
# "all" or "rebuild" or "clean" or an object file name, $t is 
# target name (file to build or rebuild/clean), and $p
# is the project directory. The default if this command is empty
# is "make -f $f $a $e".
command=S               \\ Optional command to use.