Re: [Boost-build] SHELL and trailing newlines

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-05 01:24:07

On Wednesday 04 October 2006 23:14, Johan Nilsson wrote:
> "Rene Rivera" <grafikrobot_at_[hidden]> skrev i meddelandet
> news:452406C8.6010104_at_gmail.com...
>
> [snip]
>
> > Actually it doesn't have to do with specifically with the trailing
> > newline. In Unix shells, bash, sh, ksh, etc. it will filter the output
> > of command output as arguments (``) such that it replaces all new-lines
> > with a space. For example try doing "echo `ls -1`". Since we have to
> > handle the case where want to see the new-lines, i.e. the complete raw
> > output I'd suggest adding another output processing option to
> > SHELL/COMMAND to act as the CLI shell do. Perhaps an
> > "eol-delimited-output":
> >
> >   LIBXML_INCLUDES = [ SHELL "pkg-config --cflags libxml-2.0" :
> > eol-delimited-output ] ;
> >
> > One might want to implement a 'ws-delimited-output' at the same time :-)
>
> Why not use MATCH on the output to remove whatever you want? Or am I
> missing something?

FWIW, I had no luck at all getting MATCH to work. I've tried:

local x = [ SHELL "pkg-config --cflags libxml-2.0" ] ;
echo "X : $(x) : X" ;

local xs = [ MATCH "(.*)\\n" : $(x) ] ;
echo "Xs : $(xs) : Xs" :

and got:

X : -I/usr/include/libxml2
 : X
Xs : -I/usr/i : Xs

and then I've tried just one slash before 'n' and got the same. 

- Volodya

>
> // Johan
>
>
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2