Page Comparison

...

1. SourceFilesSearchPaths declaration:
   

   To define the "search paths" for the source files. The order of the FilePaths in the SourceFilesSearchPaths declarations defines the order of the "file directories to be searched" for the specified source files. The current directory, i.e. the directory of the actual EDMcompilerProjectFile will always be searched last in the search order. This directory can be moved forward in the search order by specifying it in a SourceFilesSearchPaths declaration.

    SourceFilesSearchPaths declaration example: 

   Code Block
   SOURCE_FILES_PATHS "c:/EDMdevelopersStudio/MappingProject/" -- absolute path to "./"source files "./" -- path to source files in directory where the file is --stored current working directory "./../../utilities/" -- relative path to source files (taking into account known bug in (* relative path *its parsing) END_SOURCE_FILES_PATHS; : GENERIC; -- always INDETERMINATE for procedures

   The SourceFilesSearchPaths declaration starts with the "SOURCE_FILES_PATHS" token and end with the "END_SOURCE_FILES_PATHS" token.  There can be zero to any numbers of SourceFilesSearchPaths declarations in an EDMcompilerProjectFile. Hence, this declaration is optional; there may be zero to any number of FilePath definitions in one SourceFilesSearchPaths declaration. Each FilePath must be embedded in double quotes to enable all legal file path names. There may be any number of FilePath definitions on each line.The Express comments "--" (end-of-line) and "(* *)" (multi lines) are supported anywhere in the EDMcompilerProjectFile. However, nested multiline comments are not supported.

2. SourceFiles declarations:

...

SourceFiles declaration example:

SOURCE_FILES
   -- main file (should be placed on one of the path listed above in SOURCE_FILES_PATHS section)
   "ESS_to_DEX11_multiFiles.xpx"
   --Main file additional files (will be added to main)
   "identification_wrapper_functions.inn"
   "product_property_wrapper_functions.inn"
   "indep_prop_wrapper_functions.inn"
   "process_property_wrapper_functions.inn"
   "ass_time_wrapper_functions.inn"
  (*---------------------------------------------------------------------------------------------------------------------*)
  (*                EVERYTHING BELOW THIS IS TEMPLATE FUNCTIONS                               *)
  (*---------------------------------------------------------------------------------------------------------------------*)
    -- additional files in subfolder templateAPI 
   "templateAPI/utils.inn"
   "templateAPI/assigning_scheme_subject.inn"
   "templateAPI/representing_person_in_organization.inn"
  END_SOURCE_FILES;

...

The SourceFiles declaration starts with the "SOURCE_FILES" token and end with the "END_SOURCE_FILES" token. A SourceFile definition must be embedded in double quotes to enable all legal file names. There may be any number of SourceFile definitions on each line. There can be zero to any number of SourceFile definitions in each SourceFiles declaration. An EDMcompilerProjectFile must at least contain one SourceFiles declaration with a minimum of one SourceFile definition. Normally the first SourceFile (main file) should be schema type dependent, i.e.,xpx, qex or .rex  for EDMmappingSchema, EDMquerySchema, and EDMruleSchema respectively. The contents of a source file can be “any” text, that will be copied (concatenated) into the actual LongForm schema. The main file will include the End-Of-Schema token (END_QUERY_SCHEMA, END_SCHEMA_MAP, END_RULE_SCHEMA). Hence, the actual End-Of-Schema token will be search for in this main file, when found it will be embedded in comments “(*END_SCHEMA_MAP;*)” and the actual End-Of-Schema token will be appended to the LongForm after the very last source file. 

 Include directive:

 An Include directive is implemented with the following format:

...