From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-05-18 05:02:14
> The latest versions of bjam (3.1.16, 3.1.17) do not handle redirection
> over stdin/stdout correctly - or, this is my understanding of what happens
> I have a setup wherein bjam call python that calls cmd to execute some
> (.bat) scripts - this is on windows:
> bjam - python - cmd - .bat - iconv > out.file
> this .bat script calls iconv, but instead of only iconv output all
> stdout ends up in my output file; echo lines from the .bat script too -
> and this makes the output useless!
> - if I run the .bat script standalone, all's well
> - if I run the python script (that calls the .bat script), again, all's
> - if I use bjam <= 3.1.14, all's well
> The setup *breaks* with bjam > 3.1.14
> Any ideas? I hope someone noticed this as well ...
> I might be able to provide a testset.
Could you please post a small reproducible test case? I'll try to
reproduce it right now but many variants & questions pop to mind (e.g.
does the batch file output to stdout or stderr or does the batch file
contain the @echo off line, etc...).
And in general... posting a reproducible test case upright greatly
increases your chances of getting help... especially if running it is a
simple create-test-folder/copy-test-case/run operation with clear
indication of what is gotten and what was expected. Without this one can
not 'quickly' look it over and possibly integrate solving the problem
into some other work but instead has to wait for some free time (e.g.
over the weekend) to attempt to reproduce it...
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