From d0ed6fd30dad0591f735f576ecf473e5243ed766 Mon Sep 17 00:00:00 2001 From: Frank Kotler Date: Wed, 27 Aug 2003 11:33:56 +0000 Subject: Alexei's patch to allow "-I" paths to be searched for "incbin"ed files --- doc/nasmdoc.src | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index 795cf53f..60bd694b 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -599,8 +599,9 @@ See also the \c{-E} option, \k{opt-E}. \S{opt-i} The \i\c{-i}\I\c{-I} Option: Include File Search Directories -When NASM sees the \i\c{%include} directive in a source file (see -\k{include}), it will search for the given file not only in the +When NASM sees the \i\c{%include} or \i\c{incbin} directive in +a source file (see \k{include} or \k{incbin}), +it will search for the given file not only in the current directory, but also in any directories specified on the command line by the use of the \c{-i} option. Therefore you can include files from a \i{macro library}, for example, by typing @@ -621,8 +622,6 @@ Under Unix, a trailing forward slash is similarly necessary. by noting that the option \c{-ifoo} will cause \c{%include "bar.i"} to search for the file \c{foobar.i}...) -\#FIXME - the above is not true - see the "backslash()" function - If you want to define a \e{standard} \i{include search path}, similar to \c{/usr/include} on Unix systems, you should place one or more \c{-i} directives in the \c{NASMENV} environment variable (see -- cgit v1.2.1