- Boost - lists.boost.org

Different Lib/CMake Layout between Pre-Build-Binaries and Build from source
by Dennis Luehring 26 Jul '21

26 Jul '21

target_link_libaries(... Boost::boost) seems not to work if the stagedir/<lib> folder is missing but the pre-build binaries missing this folder https://sourceforge.net/projects/boost/files/boost-binaries/1.75.0/ https://sourceforge.net/projects/boost/files/boost-binaries/1.75.0/boost_1_… boost_1_75_0 <boost> ... bootstrap.bat bootstrap.sh <lib64-msvc-14.1> <cmake> *.lib if i build 1.75.0 from source with b2 --toolset=msvc-14.1 --stagedir=./lib64-msvc-14.1 address-model=64 architecture=x86 link=static threading=multi i've get this hierachy c:\Boost\boost_1_75_0 <boost> ... bootstrap.bat bootstrap.sh ... <lib64-msvc-14.1> <-- stagedir <lib> <cmake> *.lib what is the very same hierarchy with Qt6 cmake-configs (so its seems to be "more" standard) C:\Qt\6.1.2 <msvc2017_64> <-- aka "stagedir" <lib> <cmake> Qt6*.lib why does the pre build binary package got a different hierarchy?

1 0

[bimap][PR RFC] Add std::initializer_list constructor
by Hu Jialun 23 Jul '21

23 Jul '21

C++11 allows list initialization for classes. STL map has been added a constructor with the signature map(initializer_list<value_type> il, const allocator_type& alloc = allocator_type()); Added a similar constructor to bimap, allowing for initialization in the form of initializer list, such as boost::bimap<double, long> tdn { {114.514, 1919}, {891.931, 810} }; --- Seems that the pull request is not being seen for a while... Could someone please take a quick look at it and possibly give some directions? :) https://github.com/boostorg/bimap/pull/31 include/boost/bimap/bimap.hpp | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/include/boost/bimap/bimap.hpp b/include/boost/bimap/bimap.hpp index 5fe7a3f..a3603e5 100644 --- a/include/boost/bimap/bimap.hpp +++ b/include/boost/bimap/bimap.hpp @@ -265,6 +265,29 @@ class bimap {} + #ifndef BOOST_NO_CXX11_HDR_INITIALIZER_LIST + bimap(std::initializer_list<BOOST_DEDUCED_TYPENAME base_::core_type::value_type> init, + const allocator_type& al = allocator_type()) : + + base_::relation_set( + ::boost::multi_index::get< + BOOST_DEDUCED_TYPENAME base_::logic_relation_set_tag>(core) + ), + + core(init,ctor_args_list(),al), + + left ( + ::boost::multi_index::get< + BOOST_DEDUCED_TYPENAME base_::logic_left_tag>(core) + ), + right ( + ::boost::multi_index::get< + BOOST_DEDUCED_TYPENAME base_::logic_right_tag>(core) + ) + + {} + #endif + bimap(const bimap& x) : base_::relation_set(

1 0

CMake: using boosts own package finding stuff, howto?
by Dennis Luehring 19 Jul '21

19 Jul '21

in short: CMake does need to change (i'll need to wait for updates) to support newer released boost versions i've heard that Boost supports cmake now directly but i don't get the direct cmake support of boost working with my CMakeLists.txt i know that CMake supports 1.75 in the lastest releases directly but 1.76 and 1.77 are still not on the list and i don't want to wait for CMake release to test new features/betas etc. my system: Ubuntu 21.04/x64, CMake 3.19.4/3.21.0, GCC 10.x Boost 1.75 (want to upgrade to 1.76 soon) my boost build: mkdir ~/dev/3rdparty-liux-gcc cd ~/dev/3rdparty-linux-gcc wget https://dl.bintray.com/boostorg/release/1.75.0/source/boost_1_75_0.tar.bz2 tar -xf boost_1_75_0.tar.bz2 ln -s boost_1_75_0 ./boost cd boost_1_75_0 ./bootstrap.sh ./b2 --toolset=gcc cxxflags=-fPIC --build-dir=./_build address-model=64 architecture=x86 link=static threading=multi --with-graph --with-nowide --with-test --width-config --with-system --with-filesystem --stagedir=./_x64 ln -s _x64/lib lib my simple test hierarchy: boost_using_cmake_tests boost_using_cmake_tests\_build boost_using_cmake_tests\boost_using_cmake boost_using_cmake_tests\boost_using_cmake\CMakeLists.txt cmake_minimum_required (VERSION 3.16) set(Boost_NO_BOOST_CMAKE TRUE) set(Boost_NO_SYSTEM_PATHS TRUE) project (using_boost_with_cmake) set( MY_THIRD_PARTY_LIBS "~/dev/3rdparty-linux-gcc" ) set( BOOST_ROOT ${MY_THIRD_PARTY_LIBS}/boost ) set( BOOST_INCLUDEDIR ${BOOST_ROOT}/boost) set( BOOST_LIBRARYDIR ${BOOST_ROOT}/lib) find_package(Boost REQUIRED COMPONENTS unit_test_framework filesystem system) cmake run: using 3.19.4 cmake without 1.75 support ~/dev/boost_using_cmake/_build$ ../../cmake-3.19.4-linux-x86_64/bin/cmake ../boost_using_cmake/ -- The C compiler identification is GNU 10.3.0 -- The CXX compiler identification is GNU 10.3.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Warning at /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1204 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1326 (_Boost_COMPONENT_DEPENDENCIES) /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1935 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:14 (find_package) CMake Warning at /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1204 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1326 (_Boost_COMPONENT_DEPENDENCIES) /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1935 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:14 (find_package) CMake Warning at /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1204 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1326 (_Boost_COMPONENT_DEPENDENCIES) /home/linux/dev/cmake-3.19.4-Linux-x86_64/share/cmake-3.19/Modules/FindBoost.cmake:1935 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:14 (find_package) -- Found Boost: /home/linux/dev/3rdparty-linux-gcc/boost (found version "1.75.0") found components: unit_test_framework filesystem system -- Configuring done -- Generating done -- Build files have been written to: /home/linux/dev/boost_using_cmake_tests/_build it works but cmake 3.19.4 is missing direct support for 1.75 so its some way "unsupported", cmake does not detect the correct lib names automaticly, only some styles are working etc. i've talked about the problem on the cmake forum and the answer was https://discourse.cmake.org/t/fail-to-use-self-build-boost-1-75-under-ubunt… Brad King: "...However, Boost upstream now provides a proper CMake package file BoostConfig.cmake which should work for using Boost in any layout..." 1.75 is now directly supported by cmake - but now i want to use 1.76 and the problem re-occures i've tried serveral things to force cmake to use the boost own package findings stuff without any success i hope its possible to use 1.75 and 1.76 in the future without always wait for cmake to support it directly any hints what changes are needed with my CMakeLists.txt to support boost own cmake package finding (and get rid of these problems)?

4 17

boost still supports C++03?
by Oliver Kowalke 19 Jul '21

19 Jul '21

Hi, does boost still support Cpp03 or is Cpp11 the min. standard? Oliver

6 10

[1.77][multi_index] post-beta merge request
by Joaquin M López Muñoz 17 Jul '21

17 Jul '21

Hi, I'd like to merge this commit (only testing code and docs affected): https://github.com/boostorg/multi_index/commit/3dad7f38a44783c297b2d477cba2… This is a trivial change for C++23 forward compatibility (and C++<23 UB avoidance), as explained in https://github.com/boostorg/multi_index/issues/45 Best, Joaquín M López Muñoz

2 2

Integrating Boost into client project build via FetchContent
by Stefan Heinzmann 16 Jul '21

16 Jul '21

Hi all, the recent activity regarding adding CMake support to some remaining libraries (many thanks go to Peter Dimov), encouraged me to try using FetchContent to integrate Boost into client projects. I'm sure many people are interested in such a possibility in order to reduce dependencies on the build environment. The brief result seems to be: It almost works. Enough to make it interesting. The reason for my message is to ask if this is supposed to work, i.e. if I am trying something that should work, either now or in the near future, or if it is a frivolous expectation on my part. A toy project's CMakeLists.txt might look like this: ============================================================= cmake_minimum_required(VERSION 3.21) project(boost_test) include(FetchContent) set(BOOST_ENABLE_CMAKE ON) FetchContent_Declare(build_boost GIT_REPOSITORY https://github.com/boostorg/boost.git GIT_TAG boost-1.77.0.beta1 ) FetchContent_GetProperties(build_boost) if(NOT build_boost_POPULATED) FetchContent_Populate(build_boost) add_subdirectory( ${build_boost_SOURCE_DIR} ${build_boost_BINARY_DIR} EXCLUDE_FROM_ALL ) endif() add_executable(boost_test boost_test.cpp) target_link_libraries(boost_test PRIVATE Boost::format) ============================================================= The corresponding source file would look like this: ============================================================= #include <boost/format.hpp> #include <iostream> int main() { std::cout << boost::format("Hello %1%!") % "everybody"; } ============================================================= I used the CMake GUI version 3.21.0 on Windows 10 to configure the project for Visual Studio 2019 Release 16.10.3 with a 64-bit build. It produced lots of install-related errors in the generation phase, but it nevertheless pruduced a solution that successfully built the project. Now, there are of course a couple of issues, which I'd like to get your opinion on: 1. Optimized source download As listed, FetchContent pulls in the entire boost sources, regardless whether they're needed or not. This takes a significant amount of time and uses a lot of disk space for no benefit. Clearly, you would want to fetch only the sources you need, but there doesn't seem to be a good way to handle the dependencies between the various boost libraries. You could use the GIT_SUBMODULES option of FetchContent, but you'd need to list not only the libraries you directly use (Boost::format in my example above), but you also need to list the dependencies of those, which is tedious and brittle. I imagine that this can be handled via a special tool that gets invoked as a PATCH_COMMAND, which is able to scan through the submodules that have been populated and populates all its dependencies. I haven't seen such a tool anywhere, but maybe somebody has got a solution already? 2. Dealing with install Obviously, when using Boost like this, I don't want it to add installation items into the install of my own project, therefore I used the option EXCLUDE_FROM_ALL of add_subdirectory(). That doesn't eliminate all of the problems, as is evidenced by the myriad install-related errors that CMake flags up. Do you have an idea how to properly deal with that? I'm slightly out of my depth here. If you want to check this on your system, the CMake errors may prevent building. I have been able to build when generating a Visual Studio solution, but not when I openend the folder in Visual Studio directly, relying on Visual Studio's own CMake support. Of couse, if you have other suggestions, please tell! Cheers Stefan Heinzmann

2 1

[1.77] Requesting post-beta merges
by John Maddock 15 Jul '21

15 Jul '21

I have some late changes I'd like to merge to master if possible: For multiprecision, it's basically a single bug fix (for https://github.com/boostorg/multiprecision/issues/342) details here: https://github.com/boostorg/multiprecision/pull/344, note that the single CI failure is spurious. For Math, the collected changes are here: https://github.com/boostorg/math/pull/661 The really big changes here are documentation, the remaining issues fixed are documented in the PR above. There is one further change for Math, that I've neglected to cherry pick to the PR above, but it's this one: https://github.com/boostorg/math/pull/659 which fixes some invalid code that had slipped through. Many thanks! John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 2

[1.77] Permission to merge to master
by Andrey Semashev 15 Jul '21

15 Jul '21

Hi, I'd like to merge the following changes to master: https://github.com/boostorg/filesystem/commit/003f00239963e4b270a47d7e78664… https://github.com/boostorg/filesystem/commit/9e5a3e231e5a5d3c501447ca307a3… Fixes Boost.Filesystem compilation for Android and Mac OS. https://github.com/boostorg/utility/commit/6cca23a63a1c038b9afc261037548b78… Removes dependency of Boost.Utility on Boost.ContainerHash.

2 1

Master branch now closed for 1.77.0 beta release
by Marshall Clow 14 Jul '21

14 Jul '21

Please do not make any commits to the master branch. — Marshall

2 1

[release] Boost 1.77.0 beta 1 released
by Marshall Clow 14 Jul '21

14 Jul '21

Boost release 1.77.0 beta 1 is now available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.77.0.beta1/source/> The SHA256 checksums are as follows: 1aba2bf9416d71026c9e6bbd10a2b7cfb31b0950baa7ad0861dfb74984d96bd9 boost_1_77_0_b1.zip 55126d149664541ffc9fd1f41b2ec67146d69bdab92e41da4bb8610b755ca9ec boost_1_77_0_b1.7z 1aabe7704e91f4f8d97b81d03ddc21c3396f4b72fc4041f01bfcfc128bac0d73 boost_1_77_0_b1.tar.gz 3d5801790c96d2bc9ed23372c4f9fd963bc2f39fe540e35d7b4fe586ba77dfa7 boost_1_77_0_b1.tar.bz2 For details of what's in the release, see <https://www.boost.org/users/history/version_1_77_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0