path: root/doc/nasmdoc.src
diff options
authorCyrill Gorcunov <gorcunov@gmail.com>2018-10-25 23:40:42 +0300
committerCyrill Gorcunov <gorcunov@gmail.com>2018-10-26 01:29:52 +0300
commitfe2e1d469ac163a076e5cbc760cc3f4f051ee615 (patch)
tree662a0f10172b63855c640e8085d8d6fed34662eb /doc/nasmdoc.src
parent0e7f5111515df03925383d94a85e4383f635606c (diff)
doc: Clarify %include search directory semantics
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
Diffstat (limited to 'doc/nasmdoc.src')
1 files changed, 6 insertions, 10 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src
index fb140e99..782914d8 100644
--- a/doc/nasmdoc.src
+++ b/doc/nasmdoc.src
@@ -628,16 +628,12 @@ library}, for example, by typing
(As usual, a space between \c{-i} and the path name is allowed, and
-NASM, in the interests of complete source-code portability, does not
-understand the file naming conventions of the OS it is running on;
-the string you provide as an argument to the \c{-i} option will be
-prepended exactly as written to the name of the include file.
-Therefore the trailing backslash in the above example is necessary.
-Under Unix, a trailing forward slash is similarly necessary.
-(You can use this to your advantage, if you're really \i{perverse},
-by noting that the option \c{-ifoo} will cause \c{%include "bar.i"}
-to search for the file \c{foobar.i}...)
+Prior NASM 2.14 a path provided in the option has been considered as
+a verbatim copy and providing a path separator been up to a caller.
+One could implicitly concatenate a search path together with a filename.
+Still this was rather a trick than something useful. Now the trailing
+path separator is made to always present, thus \c{-ifoo} will be
+considered as the \c{-ifoo/} directory.
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