globally for all people working with the project in
@file{config.target}.
+@menu
+* Specifying Configuration Parameters::
+* Using Configuration Parameters::
+* Common Variables::
+@end menu
+
+@node Specifying Configuration Parameters, Using Configuration Parameters, Configuration and Conditional Compilation, Configuration and Conditional Compilation
@subsection Specifying Configuration Parameters
To specify names and default values of configuration parameters use the
@verbatiminclude ../tests/config/default/config.omk-correct
@end example
+@node Using Configuration Parameters, Common Variables, Specifying Configuration Parameters, Configuration and Conditional Compilation
@subsection Using Configuration Parameters
Configuration parameters can be used in two ways:
possible to include configuration parameters defined in a different
directory.
+@node Common Variables, , Using Configuration Parameters, Configuration and Conditional Compilation
@subsection Common Variables
It is common practice to use @file{config.omk} to store project-wide
@node Interfacing OMK to popular IDEs, Troubleshooting, Running OMK under Windows OS, OMK User's Manual
@section Interfacing OMK to popular IDEs
+@menu
+* KDevelop::
+* Eclipse/CDT::
+* Emacs/Vim/etc.::
+@end menu
+
+@node KDevelop, Eclipse/CDT, Interfacing OMK to popular IDEs, Interfacing OMK to popular IDEs
@subsection KDevelop
KDevelop has support for custom build systems. To use KDevelop to
@end example
@end enumerate
-
-@subsection Eclipse
-
+@node Eclipse/CDT, Emacs/Vim/etc., KDevelop, Interfacing OMK to popular IDEs
+@subsection Eclipse/CDT
+TODO
+@node Emacs/Vim/etc., , Eclipse/CDT, Interfacing OMK to popular IDEs
@subsection Emacs, VIM, etc.
Since OMK compilation is started by executing @command{make} command,