On Thursday 12 of June 2014 07:59:45 erik quanstrom wrote:
>
> great. glad that worked. though it is always a bit sad
> when one has to outwit one's tools.
>
still better than managing an anthill^W^W a pile of .xml `build specs'
--
dexen deVries
[[[↓][→]]]
> thanks, tried and works.
>
>
> used sed for quoting; end result is perl-ugly:
>
> alljs=`{find -name '*.js' | 9 sed 's/''//g; s/^|$/''/g' }
> or
> alljs=`{find -name '*.js' | 9 sed 's/^|$|''/&''/g' }
great. glad that worked. though it is always a bit sad
when one has to outwit one's too
On Thursday 12 of June 2014 07:41:51 erik quanstrom wrote:
>
> i was demoing a technique that you might use. have you tried it?
>
thanks, tried and works.
used sed for quoting; end result is perl-ugly:
alljs=`{find -name '*.js' | 9 sed 's/''//g; s/^|$/''/g' }
or
alljs=`{find -name '*.js
> here the var is processed by Rc inside recipe; in my case i need it processed
> by Mk inside prerequisite list
i was demoing a technique that you might use. have you tried it?
- erik
On Thursday 12 of June 2014 07:27:18 erik quanstrom wrote:
> > 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 a
> 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
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.
in Rc, i could set $ifs to bare LF and be done with it. can equivalent be
