Le 19/04/13 17:21, Pierre T. a écrit :
On 04/19/2013 05:01 PM, Steven Watanabe wrote:
AMDG
On 04/19/2013 07:36 AM, Pierre T. wrote:
I gave a try at the implementation of the expected_or_error class. I used the boost layout to package the implementation, you can download it here : http://www.hyc.io/boost/expected.zip Finally, feel free to explore the documentation I wrote http://www.hyc.io/boost/index.html
Note: In the example folder, the "b2" command never terminates (but correctly generates binaries), I can't figure out why.
Is any subprocess still running? b2 doesn't print any output for a command until it finishes (to avoid interleaving for parallel builds), so the last output is an action that has completed successfully, /not/ the action that is currently running. What platform is this on? I'm not sure what you mean with "subprocess", only the b2 command is returned by "ps -a | grep b2". Here the output of b2 :
...found 31 targets... ...updating 15 targets... common.mkdir bin common.mkdir bin/expected_or_error_example.test common.mkdir bin/expected_or_error_example.test/gcc-4.7 common.mkdir bin/expected_or_error_example.test/gcc-4.7/debug gcc.compile.c++ bin/expected_or_error_example.test/gcc-4.7/debug/expected_or_error_example.o gcc.link bin/expected_or_error_example.test/gcc-4.7/debug/expected_or_error_example ^C
I'm on Linux (Ubuntu). But on this same platform, I already successful run bjam with another project.
I suspect that your program is expecting you give the password, but when you use b2 you can not even see the request for it. Steve is there a way to give a file as input to the test? How we should bjam setup this kind of examples so that we can interact with stdin/stdout? Best, Vicente Best, Vicente