OpenMake Meister

Wild Card and Directory Dependencies

During the build process, files are found in Reference Directories that are grouped into Dependency Directories.  The build process will scan each directory in the Dependency Directory and look for files that match to any wildcard Dependency.  The build then looks to see if a found file is an Excluded dependency.

Because the build searches through the Dependency Directory directories and applies the wildcard pattern to the dependencies, it is not useful to apply an absolute file pattern match in the dependency. A leading drive letter (Windows) or forward-slash (UNIX) will invalidate the matching pattern.

For example:

Using the following Dependency Directory:

/opt/ref/Prod/src/

The file  com/package/online/Interface.java is searched relative to the Dependency Directory.  The concatenation of the two would be:

/opt/ref/Prod/src/com/package/online/Interface.java

Dependency Directory  | Dependency File

The wildcard pattern for a Target Dependency –

/opt/**/com/package/online/**/*.java

will not work, because the build would search for a dependency and Dependency Directory concatenation as follows:

     /opt/ref/Prod/src/opt/**/com/package/online/Interface.java

      Dependency Directory | Dependency File