| | 9 | It seems there are a significant number of {{{bjam}}} invocations for which there is a sensible interpretation, but for which Boost.Build currently generates an error instead and refuses to build. For example, given the following Jamfile: |
| | 10 | {{{ |
| | 11 | lib a : a.cpp : <debug-symbols>off ; |
| | 12 | lib a : a-dbg.cpp : <debug-symbols>on <profiling>on ; |
| | 13 | }}} |
| | 14 | |
| | 15 | In response to |
| | 16 | {{{ |
| | 17 | bjam debug-symbols=on |
| | 18 | }}}, |
| | 19 | the result is |
| | 20 | {{{ |
| | 21 | error: No best alternative for ./a |
| | 22 | next alternative: required properties: <debug-symbols>off |
| | 23 | not matched |
| | 24 | next alternative: required properties: <debug-symbols>on <profiling>on |
| | 25 | not matched |
| | 26 | }}} |