As of today, if you run: ./bootstrap.sh ./bjam in trunk, then the build will immediately stop on any error. The same is true with bootstrap.bat on Windows. The previously behaviour was to continue building other targets that don't depend on the failed one. The "keep going" behaviour has some good properties, for experienced users, but for new users of Boost, it was sufficiently confusing: - It's easy to miss compilation error, and then you learn that something has failed at the end of build - There's no clean at-the-end summary of what has failed, and what to do - Some users don't even know how to capture build output for further analysis, and the build output, with all the errors, can easily overflow scrollback buffers of console windows The new behaviour is implemented by writing an option into project-config.jam. Anybody who wants the old behaviour can edit that file, or pass --keep-going on the command line. The change does not affect regression tests. - Volodya
Vladimir Prus wrote:
As of today, if you run:
./bootstrap.sh ./bjam
in trunk, then the build will immediately stop on any error. The same is true with bootstrap.bat on Windows. The previously behaviour was to continue building other targets that don't depend on the failed one.
The "keep going" behaviour has some good properties, for experienced users, but for new users of Boost, it was sufficiently confusing:
- It's easy to miss compilation error, and then you learn that something has failed at the end of build - There's no clean at-the-end summary of what has failed, and what to do - Some users don't even know how to capture build output for further analysis, and the build output, with all the errors, can easily overflow scrollback buffers of console windows
The new behaviour is implemented by writing an option into project-config.jam. Anybody who wants the old behaviour can edit that file, or pass --keep-going on the command line. The change does not affect regression tests.
Hi, is there a short option like -k (-i ignore)? Vicente -- View this message in context: http://old.nabble.com/-buiild--stop-on-first-error-tp26561439p26568622.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Vicente Botet Escriba wrote:
Vladimir Prus wrote:
As of today, if you run:
./bootstrap.sh ./bjam
in trunk, then the build will immediately stop on any error. The same is true with bootstrap.bat on Windows. The previously behaviour was to continue building other targets that don't depend on the failed one.
The "keep going" behaviour has some good properties, for experienced users, but for new users of Boost, it was sufficiently confusing:
- It's easy to miss compilation error, and then you learn that something has failed at the end of build - There's no clean at-the-end summary of what has failed, and what to do - Some users don't even know how to capture build output for further analysis, and the build output, with all the errors, can easily overflow scrollback buffers of console windows
The new behaviour is implemented by writing an option into project-config.jam. Anybody who wants the old behaviour can edit that file, or pass --keep-going on the command line. The change does not affect regression tests.
Hi,
is there a short option like -k (-i ignore)?
Not at present. Do you think it's necessary? I kinda assume that as long as a user is familiar with Boost.Build enough, he'd toggle keep-going globally. - Volodya
Vladimir Prus-3 wrote:
Vicente Botet Escriba wrote:
Vladimir Prus wrote:
The new behaviour is implemented by writing an option into project-config.jam. Anybody who wants the old behaviour can edit that file, or pass --keep-going on the command line. The change does not affect regression tests.
Hi,
is there a short option like -k (-i ignore)?
Not at present. Do you think it's necessary? I kinda assume that as long as a user is familiar with Boost.Build enough, he'd toggle keep-going globally.
- Volodya
Maybe, but as you provide a command line option --keep-going, I just was interested in knowing id there was an abbreviated form. I can live without of course. Best, Vicente -- View this message in context: http://old.nabble.com/-buiild--stop-on-first-error-tp26561439p26573922.html Sent from the Boost - Dev mailing list archive at Nabble.com.
participants (3)
-
Vicente Botet Escriba -
Vladimir Prus -
Vladimir Prus