Boost logo

Boost-Build :

Subject: Re: [Boost-build] feature, properties, variants, and all the rest
From: Robert (r.firl_at_[hidden])
Date: 2017-07-28 22:52:29


On 1/13/2017 2:08 PM, Steven Watanabe wrote:
> AMDG
>
> On 01/13/2017 12:24 PM, Stefan Seefeld wrote:
>>
>> ('bjam' is the tool's name on Fedora 25, coming from the boost-jam-1.60
>> package)
>>
>> Is the `--help` flag newer than 1.60 ? (In my boost repo, I can of
>> course reproduce that `b2 --help` reports all those options.)
>>
>
> The boost-build package on Fedora is
> missing options/help.jam. The reason for
> this appears to be that it's skipped by the
> install script for Boost.Build.
>
Here are all of the command line text outputs from running "b2.exe
--help" and its variations. This version is from an Intel 17.0, Update
4.0 on Windows 8.1 Pro, Boost 1.64, x64 architecture, b2.exe

C:\Boost\bin>b2 --help
Boost.Build 2015.07-git

General command line usage:

     b2 [options] [properties] [targets]

   Options, properties and targets can be specified in any order.

Important Options:

   * --clean Remove targets instead of building
   * -a Rebuild everything
   * -n Don't execute the commands, only print them
   * -d+2 Show commands as they are executed
   * -d0 Suppress all informational messages
   * -q Stop at first error
   * --reconfigure Rerun all configuration checks
   * --debug-configuration Diagnose configuration
   * --debug-building Report which targets are built with what properties
   * --debug-generator Diagnose generator search/execution

Further Help:

   The following options can be used to obtain additional documentation.

   * --help-options Print more obscure command line options.
   * --help-internal Boost.Build implementation details.
   * --help-doc-options Implementation details doc formatting.

   C:\Boost\bin>b2 --help-options
Boost.Build Usage:

   b2 [ options... ] targets...

   * -a; Build all targets, even if they are current.
   * -fx; Read 'x' as the Jamfile for building instead of searching for the
     Boost.Build system.
   * -jx; Run up to 'x' commands concurrently.
   * -n; Do not execute build commands. Instead print out the commands
as they
     would be executed if building.
   * -ox; Output the used build commands to file 'x'.
   * -q; Quit as soon as a build failure is encountered. Without this option
     Boost.Jam will continue building as many targets as it can.
   * -sx=y; Sets a Jam variable 'x' to the value 'y', overriding any
value that
     variable would have from the environment.
   * -tx; Rebuild the target 'x', even if it is up-to-date.
   * -v; Display the version of b2.
   * --x; Any option not explicitly handled by Boost.Build remains
available to
     build scripts using the 'ARGV' variable.
   * --abbreviate-paths; Use abbreviated paths for targets.
   * --hash; Shorten target paths by using an MD5 hash.
   * -dn; Enables output of diagnostic messages. The debug level 'n' and all
     below it are enabled by this option.
   * -d+n; Enables output of diagnostic messages. Only the output for debug
     level 'n' is enabled.

Debug Levels:

   Each debug level shows a different set of information. Usually with
higher
   levels producing more verbose information. The following levels are
supported:

   * 0; Turn off all diagnostic output. Only errors are reported.
   * 1; Show the actions taken for building targets, as they are executed.
   * 2; Show quiet actions and display all action text, as they are
executed.
   * 3; Show dependency analysis, and target/source timestamps/paths.
   * 4; Show arguments of shell invocations.
   * 5; Show rule invocations and variable expansions.
   * 6; Show directory/header file/archive scans, and attempts at binding to
     targets.
   * 7; Show variable settings.
   * 8; Show variable fetches, variable expansions, and evaluation of 'if'
     expressions.
   * 9; Show variable manipulation, scanner tokens, and memory usage.
   * 10; Show execution times for rules.
   * 11; Show parsing progress of Jamfiles.
   * 12; Show graph for target dependencies.
   * 13; Show changes in target status (fate).

C:\Boost\bin>b2 --help-internal
Modules:

   These are all the known modules. Use --help <module> to get more detailed
   information.

   * ac:
   * acc:
   * alias:
   * assert:
   * auto-index:
   * bison:
   * boost:
   * boostbook:
   * boostbook-config:
   * borland:
   * build-request:
   * build-system:
   * builtin:
   * bzip2:
   * cast:
   * clang: This is a generic 'clang' toolset.
   * clang-darwin:
   * clang-linux:
   * clang-win:
   * class: Polymorphic class system built on top of core Jam facilities.
   * common:
   * common_clang_vc:
   * como:
   * como-linux:
   * como-win: The following #// line will be used by the regression
test table
     generation program as the column heading for HTML tables.
   * config-cache:
   * configure:
   * container: Base for container objects.
   * convert:
   * cray:
   * cw:
   * cw-config:
   * cygwin:
   * darwin:
   * dmc: The following #// line will be used by the regression test table
     generation program as the column heading for HTML tables.
   * doc:
   * docutils:
   * doxygen:
   * doxygen-config:
   * emscripten:
   * errors:
   * feature:
   * fop:
   * fortran:
   * gcc:
   * generate:
   * generators:
   * gettext:
   * gfortran:
   * hp_cxx:
   * hpfortran:
   * ifort:
   * indirect:
   * intel:
   * intel-darwin:
   * intel-linux:
   * intel-win:
   * lex:
   * libjpeg:
   * libpng:
   * libtiff:
   * link:
   * make:
   * mc:
   * message:
   * midl:
   * mipspro:
   * modular:
   * modules:
   * mpi:
   * msvc:
   * msvc-config:
   * notfile:
   * numbers:
   * option:
   * order:
   * os:
   * package: Example usage: package.install boost : <properties> :
<binaries> :
     <libraries> : <headers> ; This will install binaries, libraries and
headers
     to the 'proper' location, given by command line options --prefix,
     --exec-prefix, --bindir, --libdir and --includedir.
   * path:
   * pathscale:
   * pch:
   * pgi:
   * print:
   * project:
   * property:
   * property-set:
   * python-config:
   * qcc:
   * qt:
   * qt3:
   * qt4:
   * qt5: The .qrc processing utility supports various command line
option (see
     http://qt-project.org/doc/qt-5.0/rcc.html for a complete list).
   * quickbook:
   * quickbook-config:
   * rc:
   * regex:
   * scanner:
   * sequence:
   * set:
   * stage:
   * string:
   * sun:
   * symlink:
   * targets:
   * testing-aux:
   * tntnet:
   * toolset:
   * type:
   * unix:
   * utility:
   * vacpp:
   * version:
   * virtual-target:
   * vmsdecc:
   * whale: This module implements support for Whale/Dolphin/WD parser/lexer
     tools.
   * wxFormBuilder:

   * xlcpp:
   * xlf:
   * xsltproc:
   * xsltproc-config:
   * zlib: Supports the zlib library After 'using zlib', the following
targets
     are available: /zlib//zlib -- The zlib library.

   C:\Boost\bin>b2 --help-doc-options
Help Options:

   These are all the options available for enabling or disabling to
control the
   help system in various ways. Options can be enabled or disabled with
   '--help-enable-<option>', and '--help-disable-<option>' respectively.

   * debug: Generate debug output as the help is generated and modules are
     parsed. Default is disabled.
   * detailed: When showing documentation for a module, whether to also
generate
     automatically the detailed docs for each item in the module. Default is
     disabled.
   * show-locals: Whether to include local rules in help output. Default is
     disabled.

> In Christ,
> Steven Watanabe
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>


Boost-Build 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