www.creosite.com© O. Corten

wildfire5 config.pro option documentation for: SEARCH_PATH            

( ( ( (

search_path

search_path
<directory path>
specifies an ordered list of directories in which to search for object or file retrieval. these directories, along with the current (working) directory and any directories in the search.profile (see the configuration file option search_path_file) make up the creo elements/pro search path.
separator characters and search paths
you must enclose in quotation marks any search path with a separator character (space, comma, or semicolon) in a directory name, for example:
  windows: search_path "c:\program files\proe2001\models"
  unix: search_path "/home/user/smith/odd,dir;name"
note
for windows nt, omit the last backslash (\) from the path, or enclose the path in quotation marks, or add a trailing space after the backslash.
relative and absolute paths
the directory path names can be relative or absolute. you can use special characters, such as ".." in unix and windows, in specifying a relative path name.
relative path names are initially resolved relative to the startup directory. if you subsequently reload the configuration file, the system reevaluates the relative path names relative to the current working directory and appends the new directories (if any) to the search path (the previous path remains in place).
it is better, therefore, to specify the full path names always (in other words, from root) so as to avoid problems if you change working directories or use the same configuration file in another startup directory.
using more than one path
the option can have several path names on a single line, separated by commas, semicolons, or spaces. whichever delimiter you choose, you must then use consistently. the option can appear any number of times in the configuration file, so it is not necessary to have more than one path name to a line. if objects with the same name are stored in more than one search-path directory, the system retrieves the first one that it finds, regardless of which object is the most recent.
previously defined environment variables
search paths may also include previously defined environment variables. this is done by preceding the variable with $in the search path definition. for example, the environment variable obj_typecan be used as follows:
search_path /partlib/$obj_type/objs