Lines Matching +full:user +full:- +full:config
2 Boost.Config
22 even if you replace the compiler's standard library with a third-party
35 [section The <boost/config.hpp> header]
44 them usable by both Boost library and user code.
50 Boost libraries, not user code, so they can change at any time (though no
54 Boost library user code can be adversely affected by changes to the macros
56 user code is to monitor the discussions on the Boost developers list.
72 cd into ['<boost-root>]`/libs/config/` and type:
78 auto-detects your compiler if it's called g++, c++ or CC. If you are using
86 [[CXXFLAGS][The compiler flags to use, for example `-O2`. ]]
87 [[LDFLAGS ][The linker flags to use, for example `-L/mypath`. ]]
88 [[LIBS ][Any libraries to link in, for example `-lpthread`.]]
95 export CXXFLAGS="-Aa -DAportable -D__HPACC_THREAD_SAFE_RB_TREE \
96 -DRWSTD_MULTI_THREAD -DRW_MULTI_THREAD -D_REENTRANT -D_THREAD_SAFE"
97 export LDFLAGS="-DAportable"
98 export LIBS="-lpthread"
102 new header -`user.hpp`- located in the ['<boost-root>]`/libs/config/`
105 generated by the configure script, plus a header-section that contains
106 the user settable options from the default version of
111 the default user.hpp provided by boost. This option allows only one
112 configure-generated setup; boost developers should avoid this option,
113 as it incurs the danger of accidentally committing a configure-modified
119 example create a new sub-directory __BOOST_CONFIG_DIR__ `user/`, and copy
120 the header there; for example as `multithread-gcc-config.hpp`. Then, when
122 `-DBOOST_USER_CONFIG="<boost/config/user/multithread-gcc-config.hpp>"`, and
125 from the boost source - so that updates to the source do not interfere
132 [section User settable options]
134 There are some configuration-options that represent user choices, rather
136 `<boost/config/user.hpp>` and at the start of a configure-generated `user.hpp`
138 `<boost/config/user.hpp>`, they are listed in the following table:
147 When defined, it should point to the name of the user configuration file
149 defaults to [@../../../../boost/config/user.hpp `<boost/config/user.hpp>`].
156 to [@../../../../boost/config/compiler/gcc.hpp `<boost/config/compiler/gcc.hpp>`].
164 [@../../../../boost/config/stdlib/stlport.hpp `<boost/config/stdlib/stlport.hpp>`].
171 to [@../../../../boost/config/platform/linux.hpp `<boost/config/platform/linux.hpp>`].
176 the user header (see `BOOST_USER_CONFIG`), has had any options necessary
182 where the user header (see `BOOST_USER_CONFIG`), has had any options necessary
188 no useful extra features), or where the user header (see
205 When this flag is set, if the config finds anything unknown, then it will
218 config system when it detects that the compiler is in "strict mode".
225 A prefix header to include in place of whatever boost.config would normally
230 A suffix header to include in place of whatever boost.config would normally
254 Tells the config system not to automatically select which libraries to link
262 Tells the config system not to automatically select which library to link
271 Causes the auto-linking code to output diagnostic messages indicating the
275 If you built Boost using the `--buildid` option then set this macro to the same value
276 as you passed to bjam. For example if you built using `bjam address-model=64 --buildid=amd64`
277 then compile your code with `-DBOOST_LIB_BUILDID=amd64` to ensure the correct libraries
295 Boost's configuration is structured so that the user-configuration is
297 is not defined). This sets up any user-defined policies, and gives the
298 user-configuration a chance to influence what happens next.
302 [link config_user_settable see user settable macros]), and if the corresponding
304 library/platform is in use is included in order to set these. The config
307 disable including any compiler configuration file -
308 [link config_user_settable see user settable macros]).
311 this header contains any boiler plate configuration code - for example where one
323 boost config has been updated for more recent versions of Visual C++ or STLport.
325 [@../../../../boost/config/compiler/visualc.hpp `<boost/config/compiler/visualc.hpp>`]
327 [@../../../../boost/config/stdlib/stlport.hpp `<boost/config/stdlib/stlport.hpp>`]
329 [@../../../../boost/config/platform/win32.hpp `<boost/config/platform/win32.hpp>`]
331 `boost/config/mysetup/`, and copy the configuration files into there. Finally,
334 #define BOOST_COMPILER_CONFIG "boost/config/mysetup/visualc.hpp"
335 #define BOOST_STDLIB_CONFIG "boost/config/mysetup/stlport.hpp"
336 #define BOOST_USER_CONFIG "boost/config/mysetup/win32.hpp"
362 If you are working on a unix-like platform then you can use the configure script to
363 generate a "frozen" configuration based on your current compiler setup -
373 under the __BOOST_CONFIG_DIR__ `test/` sub-directory:
398 does not then the corresponding `BOOST_NO_XXX` macro needs to be defined - see
404 not be - see each test file for specific details.
408 corresponding `BOOST_HAS_XXX` macro is defined when it should not be - see
413 corresponding `BOOST_HAS_XXX` macro can be safely defined - see each test
424 [: `./configure --enable-test`]