Terminology and Syntax Notation
The MAKE_APP tool-set is using ASCII-based configuration file to describe how to process single software solution. This configuration file MUST be named as make_app.config (lower-case only!) and maintained into the root-directory of your solution. The root-directory is used by MAKE_APP to calculate other relative to the project sub-directories, and to keep also the portability of the entire solution - for example, you can move the solution to another file system tree branching and the configuration should not be changed and MAKE_APP will work in the same way. The configuration file consists of well-formed sets of Erlang terms and data types encoded in ISO-8859-1 (Latin-1) characters called configuration elements. Each configuration element MUST end with a single dot. Do not forget this DOT after each element, otherwise your configuration shall be misspelled and rejected. Take into consideration that MAKE_APP is interpreting only particular subset of terms required for configuration purposes, therefore the current documentation covers only this subset of terms. Last but not least, the configuration elements can be used in different order. You can assemble and organize your configuration at your own style and convenience. Complete example of simple configuration file is published on page "First Steps". |
The following configuration elements are supported by MAKE_APP and can be used in make_app.config file: •{include, <extension>}. - used to activate particular configuration extension; •{solution, <solution_id>, <solution_properties>}. - used to define your software solution; •{project, <project_id>, <project_properties>}. - used to define one or more projects that could be used by the solution; •{task, <task_id>, <task_properties>}. - used to define one or more configuration tasks that could be used by your projects. |