# Copyright Vladimir Prus 2002-2006. # Copyright Dave Abrahams 2005-2006. # Copyright Rene Rivera 2005-2007. # Copyright Douglas Gregor 2005. # # Distributed under the Boost Software License, Version 1.0. # (See accompanying file LICENSE_1_0.txt or copy at # http://www.boost.org/LICENSE_1_0.txt) # Usage: # # b2 [options] [properties] [install|stage] # # Builds and installs Boost. # # Targets and Related Options: # # install Install headers and compiled library files to the # ======= configured locations (below). # # --prefix= Install architecture independent files here. # Default: C:\Boost on Windows # Default: /usr/local on Unix, Linux, etc. # # --exec-prefix= Install architecture dependent files here. # Default: # # --libdir= Install library files here. # Default: /lib # # --includedir= Install header files here. # Default: /include # # --cmakedir= Install CMake configuration files here. # Default: /cmake # # --no-cmake-config Do not install CMake configuration files. # # stage Build and install only compiled library files to the # ===== stage directory. # # --stagedir= Install library files here # Default: ./stage # # Other Options: # # --build-type= Build the specified pre-defined set of variations of # the libraries. Note, that which variants get built # depends on what each library supports. # # -- minimal -- (default) Builds a minimal set of # variants. On Windows, these are static # multithreaded libraries in debug and release # modes, using shared runtime. On Linux, these are # static and shared multithreaded libraries in # release mode. # # -- complete -- Build all possible variations. # # --build-dir=DIR Build in this location instead of building within # the distribution tree. Recommended! # # --show-libraries Display the list of Boost libraries that require # build and installation steps, and then exit. # # --layout= Determine whether to choose library names and header # locations such that multiple versions of Boost or # multiple compilers can be used on the same system. # # -- versioned -- Names of boost binaries include # the Boost version number, name and version of # the compiler and encoded build properties. Boost # headers are installed in a subdirectory of # whose name contains the Boost version # number. # # -- tagged -- Names of boost binaries include the # encoded build properties such as variant and # threading, but do not including compiler name # and version, or Boost version. This option is # useful if you build several variants of Boost, # using the same compiler. # # -- system -- Binaries names do not include the # Boost version number or the name and version # number of the compiler. Boost headers are # installed directly into . This option is # intended for system integrators building # distribution packages. # # The default value is 'versioned' on Windows, and # 'system' on Unix. # # --buildid=ID Add the specified ID to the name of built libraries. # The default is to not add anything. # # --python-buildid=ID Add the specified ID to the name of built libraries # that depend on Python. The default is to not add # anything. This ID is added in addition to --buildid. # # --help This message. # # --with- Build and install the specified . If this # option is used, only libraries specified using this # option will be built. # # --without- Do not build, stage, or install the specified # . By default, all libraries are built. # # Properties: # # toolset=toolset Indicate the toolset to build with. # # variant=debug|release Select the build variant # # link=static|shared Whether to build static or shared libraries # # threading=single|multi Whether to build single or multithreaded binaries # # runtime-link=static|shared # Whether to link to static or shared C and C++ # runtime. # # TODO: # - handle boost version # - handle python options such as pydebug import boostcpp ; import package ; import sequence ; import xsltproc ; import set ; import path ; import link ; import notfile ; import virtual-target ; import "class" : new ; import property-set ; import threadapi-feature ; import option ; import property ; # Backslash because of `bcp --namespace` import tools/boost\_install/boost-install ; path-constant BOOST_ROOT : . ; constant BOOST_VERSION : 1.84.0 ; constant BOOST_JAMROOT_MODULE : $(__name__) ; # Allow subprojects to simply `import config : requires ;` to get access to the requires rule modules.poke : BOOST_BUILD_PATH : $(BOOST_ROOT)/libs/config/checks [ modules.peek : BOOST_BUILD_PATH ] ; boostcpp.set-version $(BOOST_VERSION) ; use-project /boost/architecture : libs/config/checks/architecture ; local all-headers = [ MATCH .*libs/(.*)/include/boost : [ glob libs/*/include/boost libs/*/*/include/boost ] ] ; for dir in $(all-headers) { link-directory $(dir)-headers : libs/$(dir)/include/boost : . ; explicit $(dir)-headers ; } if $(all-headers) { constant BOOST_MODULARLAYOUT : $(all-headers) ; } project boost : requirements . [ boostcpp.architecture ] [ boostcpp.address-model ] # Disable auto-linking for all targets here, primarily because it caused # troubles with V2. BOOST_ALL_NO_LIB=1 # Used to encode variant in target name. See the 'tag' rule below. @$(__name__).tag @handle-static-runtime @clang-darwin-cxxstd-11 # Comeau does not support shared lib como:static como-linux:_GNU_SOURCE=1 # When building docs within Boost, we want the standard Boost style boost.defaults=Boost @threadapi-feature.detect : usage-requirements . : default-build hidden multi : build-dir bin.v2 ; # This rule is called by Boost.Build to determine the name of target. We use it # to encode the build variant, compiler name and boost version in the target # name. # rule tag ( name : type ? : property-set ) { return [ boostcpp.tag $(name) : $(type) : $(property-set) ] ; } rule python-tag ( name : type ? : property-set ) { return [ boostcpp.python-tag $(name) : $(type) : $(property-set) ] ; } rule handle-static-runtime ( properties * ) { # Using static runtime with shared libraries is impossible on Linux, and # dangerous on Windows. Therefore, we disallow it. This might be drastic, # but it was disabled for a while without anybody complaining. local argv = [ modules.peek : ARGV ] ; if shared in $(properties) && static in $(properties) # For CW, static runtime is needed so that std::locale works. && ! ( cw in $(properties) ) && ! --allow-shared-static in $(argv) { boostcpp.emit-shared-static-warning ; return no ; } } rule clang-darwin-cxxstd-11 ( properties * ) { # AppleClang defaults to C++03 local result = [ property.select : $(properties) ] ; if darwin in $(properties) { result ?= 11 ; } return $(result) ; } all-libraries = [ MATCH .*libs/(.*)/build/.* : [ glob libs/*/build/Jamfile.v2 ] [ glob libs/*/build/Jamfile ] ] ; all-libraries = [ sequence.unique $(all-libraries) ] ; # The function_types library has a Jamfile, but it's used for maintenance # purposes, there's no library to build and install. all-libraries = [ set.difference $(all-libraries) : function_types ] ; # Setup convenient aliases for all libraries. local rule explicit-alias ( id : targets + ) { alias $(id) : $(targets) ; explicit $(id) ; } # First, the complicated libraries: where the target name in Jamfile is # different from its directory name. explicit-alias prg_exec_monitor : libs/test/build//boost_prg_exec_monitor ; explicit-alias test_exec_monitor : libs/test/build//boost_test_exec_monitor ; explicit-alias unit_test_framework : libs/test/build//boost_unit_test_framework ; explicit-alias serialization : libs/serialization/build//boost_serialization ; explicit-alias wserialization : libs/serialization/build//boost_wserialization ; for local l in $(all-libraries) { if ! $(l) in test graph serialization headers { explicit-alias $(l) : libs/$(l)/build//boost_$(l) ; } } # Log has an additional target explicit-alias log_setup : libs/log/build//boost_log_setup ; rule do-nothing { } rule generate-alias ( project name : property-set : sources * ) { local action-name = [ $(property-set).get ] ; local m = [ MATCH ^@(.*) : $(action-name) ] ; property-set = [ property-set.empty ] ; local action = [ new action $(sources) : $(m[1]) : $(property-set) ] ; local t = [ new notfile-target $(name) : $(project) : $(action) ] ; return [ virtual-target.register $(t) ] ; } generate headers : $(all-headers)-headers : @generate-alias @do-nothing : : . ; #alias headers : $(all-headers)-headers : : : . ; explicit headers ; # Make project ids of all libraries known. for local l in $(all-libraries) { use-project /boost/$(l) : libs/$(l)/build ; } if [ path.exists $(BOOST_ROOT)/tools/inspect/build ] { use-project /boost/tools/inspect : tools/inspect/build ; } if [ path.exists $(BOOST_ROOT)/libs/wave/tool/build ] { use-project /boost/libs/wave/tool : libs/wave/tool/build ; } # Make the boost-install rule visible in subprojects # This rule should be called from libraries' Jamfiles and will create two # targets, "install" and "stage", that will install or stage that library. The # --prefix option is respected, but --with and --without options, naturally, are # ignored. # # - libraries -- list of library targets to install. rule boost-install ( libraries * ) { boost-install.boost-install $(libraries) ; } # Creates a library target, adding autolink support and also creates # stage and install targets via boost-install, above. rule boost-lib ( name : sources * : requirements * : default-build * : usage-requirements * ) { autolink = shared:BOOST_$(name:U)_DYN_LINK=1 ; name = boost_$(name) ; lib $(name) : $(sources) : $(requirements) $(autolink) : $(default-build) : $(usage-requirements) $(autolink) ; boost-install $(name) ; } # Declare special top-level targets that build and install the desired variants # of the libraries. boostcpp.declare-targets $(all-libraries) ;