Subject: Re: [boost] Stop on first error
From: Dean Michael Berris (mikhailberis_at_[hidden])
Date: 2009-03-14 10:28:52
On Sat, Mar 14, 2009 at 10:16 PM, Vladimir Prus <ghost_at_[hidden]> wrote:
> Presently, when building Boost, the build process does not stop if an error
> has occurred. This is behaviour we inherited, and it differs from every
> other build system out there. We had quite a number of users confused where
> build ends with "failed N targets", with the original error scrolled away --
> it is not apparent what has caused the error, and often, the error is not even
> available from console program history.
> While experienced users might prefer being able to kick a build, go to lunch,
> and then fix a couple of failures in the middle of the build, ordinary users
> don't like it so much. So, how about we do what the rest of the world does,
> and stop build of C++ Boost on the first error?
Perhaps we can document and say "add -q to the bjam invocation if you
want the build to stop on the first error".
Although I agree this would be nice to have as the default behavior.
-- Dean Michael Berris | Software Engineer, Friendster, Inc. blog.cplusplus-soup.com | twitter.com/mikhailberis | linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis | deanberris.com
Boost 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