Boost C++ Libraries
Boost provides free peer-reviewed portable C++ source libraries. The
emphasis is on libraries that work well with the C++ Standard Library.
One goal is to establish "existing practice" and provide reference
implementations so that the Boost libraries are suitable for eventual
standardization. Some of the libraries have already been proposed for
inclusion in the C++ Standards Committee's upcoming C++ Standard
Library Technical Report.
Although Boost was begun by members of the C++ Standards Committee
Library Working Group, membership has expanded to include nearly two
thousand members of the C++ community at large.
This package is mainly needed for updating from a prior version, the
dynamic libraries are found in their respective package. For development
using Boost, you also need the boost-devel package. For documentation,
see the boost-doc package.
- Developed at devel:libraries:c_c++
- Sources inherited from project openSUSE:Factory
-
21
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:SLECandidates/boost && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
README.boost-devel | 0000000183 183 Bytes | |
__init__.py | 0000000014 14 Bytes | |
_constraints | 0000000282 282 Bytes | |
_multibuild | 0000000053 53 Bytes | |
baselibs.conf | 0000000624 624 Bytes | |
boost-1.55.0-python-test-PyImport_AppendInittab.pa |
0000002218 2.17 KB | |
boost-1.57.0-python-abi_letters.patch | 0000002339 2.28 KB | |
boost-1.57.0-python-libpython_dep.patch | 0000000454 454 Bytes | |
boost-aarch64-flags.patch | 0000000579 579 Bytes | |
boost-disable-pch-on-aarch64.patch | 0000002754 2.69 KB | |
boost-no_segfault_in_Regex_filter.patch | 0000000436 436 Bytes | |
boost-no_type_punning.patch | 0000005839 5.7 KB | |
boost-pool_check_overflow.patch | 0000001287 1.26 KB | |
boost-rpmlintrc | 0000000578 578 Bytes | |
boost-rpmoptflags-only.patch | 0000002392 2.34 KB | |
boost-strict_aliasing.patch | 0000000472 472 Bytes | |
boost-thread.patch | 0000000515 515 Bytes | |
boost-use_std_xml_catalog.patch | 0000002319 2.26 KB | |
boost-visibility.patch | 0000003912 3.82 KB | |
boost.changes | 0000078047 76.2 KB | |
boost.spec | 0000069964 68.3 KB | |
boost_1_56_pdf.tar.bz2 | 0046518400 44.4 MB | |
boost_1_67_0.tar.bz2 | 0087336566 83.3 MB | |
dynamic_linking.patch | 0000004710 4.6 KB | |
exception.objdump | 0000000108 108 Bytes | |
existing_extra_docs | 0000018839 18.4 KB | |
python_library_name.patch | 0000005104 4.98 KB | |
python_mpi.patch | 0000000744 744 Bytes | |
python_numpy_retfunc.patch | 0000000777 777 Bytes | |
symbol_diff.sh | 0000000450 450 Bytes |
Revision 123 (latest revision is 166)
- fix packaging of Boost.Contract on s390 and other platforms without Boost.Context support. - fix build on older SLE SP by owning /usr/share/licenses directory - Update to version 1.67.0 New libraries: * Contract: Contract programming for C++. All contract programming features are supported: Subcontracting, class invariants, postconditions (with old and return values), preconditions, customizable actions on assertion failure (e.g., terminate or throw), optional compilation and checking of assertions, etc, from Lorenzo Caminiti. * HOF: Higher-order functions for C++, from Paul Fultz II. Breaking changes in updated libraries: * atomic: Breaking change: Changed the result of the (op)_and_test operations added in Boost 1.66 to the opposite - the functions now return true if the operation result is non-zero. This is consistent with other test methods in Boost.Atomic and the C++ standard library. Users can define BOOST_ATOMIC_DETAIL_HIGHLIGHT_OP_AND_TEST when compiling their code to emit warnings on every use of the changed functions. This way users can locate the code that needs to be updated. * multiprecission: When converting a multiprecision integer to a narrower type, if the value is too large (or negative) to fit in the smaller type, then the result is either the maximum (or minimum) value of the target type. This was always the intended behaviour, but was somewhat haphazardly enforced before. If you really do want just the low order N bits of a value, then you will need to mask these out prior to the case, for example: static_cast<unsigned>(~static_cast<unsigned>(0) & my_value). Note that technically (to avoid undefined behaviour) you should do the same thing with built in integer types too. * spirit: Removed `with_context` utility: <boost/utility.hpp> header no longer includes boost::next and boost::prior as they have been moved to the iterator module. Instead include <boost/next_prior.hpp>. Other uses of <boost/utility.hpp> are discouraged, it's better to use the header for the specific functionality instead. * uuid: random_generator is no longer copyable Libraries that were updated: Asio, Atomic, Beast, ContainerHash, Context, Core, Coroutine2, DateTime, DLL, Fiber, Filesystem, Fusion, Locale, Log, Math, Multi-index Containers, Multiprecission, Optional, Phoenix, PolyCollection, Python, Spirit, Stacktrace, Test, TypeIndex, TypeTraits, Utility, Unordered, Units, Uuid, and Variant. For complete list of changes, see, https://www.boost.org/users/history/version_1_67_0.html - refreshed patches: * boost-strict_aliasing.patch * boost-aarch64-flags.patch - python_library_name.patch: adapted to not append version number to library names, like new boost is doing. - disable python2 builds by default - use regular Requires for libboost_header dependency
Comments 5
Boost 1.69 is the latest stable. https://www.boost.org/users/history/version_1_69_0.html
For latest version of Boost, see its devel project at https://build.opensuse.org/package/show/devel:libraries:c_c++/boost
When it's ready, it will be submitted to Factory. But there are still a few problems we would like to fix before submitting it.
Why libboost_chrono1_69_0 is missing in baselibs.conf?
comments is not a place for bug reports. we have https://bugzilla.opensuse.org for that.
And libboost_timer1_69_0 is missing too.