Configuration

General ideas

• independant from the platform (windows/unix/.NET)
• one file with multiple configurations (eg. debug, release build)
• exclude as regexp pattern
• global ignore patterns (eg. cvs/svn)
• libraries
• relative paths
• actions before/after run/compile (eg. start a server)

A system consists of multiple targets. A target can extend another target. A target can have some libraries, assemblies, clusters and override clusters. A library has an associated target. A cluster can have a parent cluster. An override cluster has a some groups it overrides.

Questions and Problems

• Specify use of other clusters? Yes
• Variables? If not defined, take environment variable.
• Path relative to ecf file? Yes
• When are two libraries the same? UUID

Multiple library usage

Problem

System Application

library A
library B

System A

library C
    option Yes

System B

library C
    option No

We have a conflict for the option on library C.

Solution

If the library is directly used in Application, use the this options, otherwise use the options of the Application system.

File pattern

The file pattern match against the relative path in unix format in a cluster. e.g. if the cluster is in C:\mycluster

   C:\mycluster\storage\table\*
   C:\mycluster\storage\table.e
   C:\mycluster\something\storage\table\*

   C:\mycluster\storage\table\*

   C:\mycluster\a\test\*
   C:\mycluster\b\test\*

   C:\mycluster\a\test\*
   C:\mycluster\b\test\*
   C:\mycluster\something\table\test\*