From a45d3157b1ac2460753e21a9e6a9b1a12b98f674 Mon Sep 17 00:00:00 2001 From: Michal Sojka Date: Thu, 17 Feb 2011 16:56:35 +0100 Subject: [PATCH] Clarify documentation about headers and libraries --- doc/omk-manual.texinfo | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/omk-manual.texinfo b/doc/omk-manual.texinfo index 2faa14a..a456863 100644 --- a/doc/omk-manual.texinfo +++ b/doc/omk-manual.texinfo @@ -404,7 +404,7 @@ source @file{test.c}. @c FIXME: INCLUDES variable should not be set by rtlinux rules. @node Libraries, Multiple Directories, Compiling Programs, User's Manual -@section Libraries +@section Compiling Libraries With OMK, you can easily create statically or dynamically linked @@ -448,12 +448,13 @@ by other programs. @subsection Header Files C and C++ libraries are not very useful without header files. OMK -provides several variables that specify activities on header files. +provides several variables that controls operations with header files. -During compilation, header files are copied (or linked) from source -directories to the @file{_compiled} tree -(see @ref{include-pass}). Libraries and programs are then compiled against -these copies. +During compilation, header files are copied (or linked by symbolic +links) from source directories to the @file{_compiled} tree (see +@ref{include-pass}). Libraries and programs are then compiled against +these copies. The following variables control which headers are copied +and what is their destination file name. @anchor{include_HEADERS} @defvar include_HEADERS -- 2.39.2