Add a tip about opt_VARS and whitespace.
Reviewed by: wblock Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D5447
This commit is contained in:
parent
bb03abb133
commit
dfc2b5dbdd
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48261
1 changed files with 16 additions and 0 deletions
|
@ -4487,6 +4487,22 @@ BIN3_BUILD= yes
|
|||
.else
|
||||
BIN3_BUILD= no
|
||||
.endif</programlisting>
|
||||
|
||||
<tip>
|
||||
<para>Values containing whitespace must be enclosed in
|
||||
quotes:</para>
|
||||
|
||||
<programlisting>OPT_VARS= foo="bar baz"</programlisting>
|
||||
|
||||
<para>This is due to the way &man.make.1; variable expansion
|
||||
deals with whitespace. When <literal>OPT_VARS= foo=bar
|
||||
baz</literal> is expanded, the variable ends up
|
||||
containing two strings, <literal>foo=bar</literal> and
|
||||
<literal>baz</literal>. But the submitter probably
|
||||
intended there to be only one string, <literal>foo=bar
|
||||
baz</literal>. Quoting the value prevents whitespace
|
||||
from being used as a delimiter.</para>
|
||||
</tip>
|
||||
</sect3>
|
||||
|
||||
<sect3 xml:id="options-dependencies">
|
||||
|
|
Loading…
Reference in a new issue