From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] $ifs equivalent in mk?
Date: Thu, 12 Jun 2014 07:27:18 -0400 [thread overview]
Message-ID: <8a792eb68d2991d4c56b4666769c7f14@mikro.quanstro.net> (raw)
In-Reply-To: <1558651.miEKvk4LTA@coil>
> i have a mkfile which does:
>
> alljs=`{find -name '*.js'}
>
> my_target:Q: ... $alljs
> my_recipe;
>
> and it breaks for files with spaces in pathname -- each space-separated token
> of pathname is treated as separate prerequisite.
if you rc-quote the terms, it should work.
; find|grep b
'./a b'
; cat mkfile
x=`{find|grep b}
all:
echo $x|wc
for(i in $x)
echo $i
; mk
echo ./a b|wc
for(i in ./a b)
echo $i
1 2 6
./a b
next prev parent reply other threads:[~2014-06-12 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 11:05 dexen deVries
2014-06-12 11:27 ` erik quanstrom [this message]
2014-06-12 11:39 ` dexen deVries
2014-06-12 11:41 ` erik quanstrom
2014-06-12 11:57 ` dexen deVries
2014-06-12 11:59 ` erik quanstrom
2014-06-12 12:06 ` dexen deVries
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a792eb68d2991d4c56b4666769c7f14@mikro.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).