Lines Matching +full:report +full:- +full:config

2     Boost.Config
29 broken compilers and encouraging non-standard subsets. Adding settings for
32 desirable feature. The boost config.hpp policy is designed to minimize the
37 * Boost library implementers are not required to "`#include <boost/config.hpp>`",
40 * If a library implementer wishes to support some non-conforming compiler,
41 or to support some platform specific feature, "`#include <boost/config.hpp>`"
45 `<climits>`, use those standard headers rather than `<boost/config.hpp>`.
46 * Boost files that use macros defined in `<boost/config.hpp>` should have
48 This means that the starting point for porting `<boost/config.hpp>` to a new
52 * If a Boost library implementer wants something added to `config.hpp`, post
54 will be honored; the intent is to limit the complexity of config.hpp.
58 * The intent is not to disable mainstream features now well-supported by the
64 The header `<boost/config/warning_disable.hpp>` can be used to disable
80 [[Visual C++ 8 and later][[@http://msdn2.microsoft.com/en-us/library/ttcz0bys(VS.80).aspx C4996]: E…
90 When you need to add a new defect macro - either to fix a problem with an
91 existing library, or when adding a new library - distil the issue down to
110 is the defect description - try and keep the file name under the Mac 30 character
126 Once the test code is in place in libs/config/test, updating the configuration
129 * cd into `libs/config/tools` and run `bjam`. This generates the `.cpp`
131 libs/config/test/all/Jamfile.v2, `config_test.cpp` and `config_info.cpp`.[br][br]
133 * cd into `libs/config/test/all` and run `bjam `['MACRONAME` compiler-list`], where
134 ['MACRONAME] is the name of the new macro, and ['`compiler-list`] is a space separated list of
136 The xxx_pass_test and the xxx_fail_test [*should both report `**passed**`].[br][br]
137 If ['MACRONAME] is not defined when it should be defined, xxx_pass_test will not report `**passed**…
138 If ['MACRONAME] is defined when it should not be defined, xxx_fail_test will not report `**passed**…
140 * cd into `libs/config/test` and run `bjam config_info config_test `['`compiler-list`].
141 `config_info` should build and run cleanly for all the compilers in ['`compiler-list`]
147 * Define the defect macro in those config headers that require it.
150 * Keep an eye on the regression tests for new failures in Boost.Config caused by
167 __BOOST_CONFIG_SUFFIX_HEADER__ to auto-detect the feature where possible
177 be relatively stable - a boost user should not have to recompile their code
187 [@../../tools/configure.in libs/config/tools/configure.in] as well.
194 [@../../../../boost/config/detail/select_compiler_config.hpp <boost/config/detail/select_compiler_c…
195 [@../../../../boost/config/detail/select_platform_config.hpp <boost/config/detail/select_platform_c…
196 [@../../../../boost/config/detail/select_stdlib_config.hpp <boost/config/detail/select_stdlib_confi…
201 platforms are ignored and assumed to be fully standards compliant - this gives
205 When adding or modifying the individual mini-configs, assume that future, as