Merge branch 'master' into sssa

[omk/sssa.git] / doc / omk-manual.texinfo

diff --git a/doc/omk-manual.texinfo b/doc/omk-manual.texinfo
index 7db130252a876930496231c530edd8b8377aea8e..c85cc52be320f7298d1ff582157429a2ed37e14f 100644 (file)
--- a/doc/omk-manual.texinfo
+++ b/doc/omk-manual.texinfo
@@ -362,9 +362,19 @@ source @file{test.c}.
   @end example
 @end defvar
 
+@defvar lib_LOADLIBES
+  This variable contains a list of libraries which needs to be linked to
+  to all programs or shared libraries in this directory.
+@end defvar
+
 @defvar LOADLIBES
-  This variable contains a list of libraries all programs in this
-  directory needs to be linked to.
+  This variable contains a list linker switches to load additional
+  libraries. You usually specify here -L and -l switches.
+
+  Note: The value of this variable is not used used by OMK for any purpose
+  other than linker invocation. Therefore dependency handling of shared
+  libraries does not work if the library is specified in LOADLIBES
+  instead of lib_LOADLIBES.
 @end defvar
 
 @defvar INCLUDES
@@ -740,9 +750,10 @@ 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
-settings. Here is the list of variables, which are commonly set here
-(but they can also be set elsewhere, e.g. in @file{Makefile.omk}).
+It is common practice to use @file{config.target} or @file{config.omk}
+to store project-wide settings. Here is the list of variables, which are
+commonly set here (but they can also be set elsewhere, e.g. in
+@file{Makefile.omk}).
 
 You can easily ``reconfigure'' your project by changing the
 @file{config.omk} file. It is useful to have several configurations