From: David Abrahams (dave_at_[hidden])
Date: 2005-09-21 11:47:32
David Abrahams <dave_at_[hidden]> writes:
> Rene Rivera <grafik.list_at_[hidden]> writes:
>> David Abrahams wrote:
>>> Someone emailed me privately to say that we could pipe our commands
>>> into cmd without ever creating a .bat file. That's an interesting
>>> idea; I'm not sure how to implement it though.
>> Really? I thought about that yesterday but the CMD.EXE docs don't
>> mention anything like that. I guess it will take some experimentation to
>> find out.
> ECHO 'dir' | cmd
> works for me.
The helpful soul sent me this:
I'm suggesting that if you have a slave CMD process and you have some set
of commands then you want it to execute for you, then you:
- use the UUID generator function to get an unique string
- pipe the commands into the slave and capture their output
- pipe echo abc12328fh8a (or whatever) as a signal
- wait for the signal text to show up on the slave output
Given that you don't see the child processes exit, you need to
know when you've got all the output from the commands that you sent.
Can't post to the list. Not from here anyway. I could subscribe
from home and do it there, but playing Forza Motorsport is more
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk