| | 1 | |
| | 2 | Users are sometimes confused about what Boost.Build does and why, and what's |
| | 3 | Jamfile, anyway. We can do this: |
| | 4 | |
| | 5 | Jamfiles of all project should start with comment saying this is Boost.Build |
| | 6 | file, and giving link to the list of rules to be used in Jamfile and jam |
| | 7 | syntax. |
| | 8 | |
| | 9 | We probably can have a version of --debug-building that is less verbose |
| | 10 | and more user-oriented: |
| | 11 | {{{ |
| | 12 | building exe:foo/bar with debug/threading=multi |
| | 13 | |
| | 14 | installing foo:.... |
| | 15 | }}} |
| | 16 | |
| | 17 | Maybe, for C++ Boost it would be valuable to list libraries that |
| | 18 | will be built in even more apparent format: |
| | 19 | {{{ |
| | 20 | Boost version 1.35.0 |
| | 21 | |
| | 22 | Configuration: |
| | 23 | |
| | 24 | bjam command......: bjam --prefix=/usr/local -stdlib=stlport --with-thread --with-circular_buffer |
| | 25 | prefix............: /usr/local |
| | 26 | debug.............: yes |
| | 27 | stdlib............: stlport <-- or standard if stlport is not used |
| | 28 | |
| | 29 | Libraries: |
| | 30 | |
| | 31 | circular buffer...: yes |
| | 32 | filesystem........: no |
| | 33 | . |
| | 34 | . |
| | 35 | . |
| | 36 | python............: no |
| | 37 | test..............: no |
| | 38 | thread............: yes |
| | 39 | }}} |