- Boost-users - lists.preview.boost.org

Boost 64bit in Embarcadero C++ Builder
by Michael Morelli 17 Mar '21

17 Mar '21

Hi folks, we are testing the Boost.Test-Framework (installed with GetIt-Package Boost). We use C++ Builder 10.4.1 with Boost 1.70.0. We have created a new C++ Console-Application (with VCL enabled). Under Project->Options we have set '_TCHAR as char', because Boost.Test seems to need this mapping. It is not working with ' _TCHAR as wchar_t' The application main-entry-function is imported via #include <boost/test/included/unit_test.hpp>. The application then is run with the params : --log_level=all --report_level=detailed --build_info=true The console-output seems to be fuzzy : 1. Why is the platform win32? We use target-platform win64 and have installed boost 64bit via getit... 2. Paths are outputted with '\' and '/' 3. The fatal-error is correct but the consoleoutput 'St9exception' seems not correctly interpreted (charset ?) Are we doing something wrong or do you have some tipps regarding this ? Thx a lot. This is the console-output : [cid:image001.png@01D71B23.032439B0] Kind regards, Michael Morelli

1 0

[release] Boost 1.76.0 beta 1 released
by Marshall Clow 16 Mar '21

16 Mar '21

Boost release 1.76.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/> The SHA256 checksums are as follows: 39eecd9672e78b95c8e3fdec1430a63788d528a66d3c8799c4639238e5d785bd boost_1_76_0_b1.7z c32edd34f767dd4bb67b86f76ebf58cf76822a5993a9b434c028b2dd08cfeefc boost_1_76_0_b1.zip 3ec1f92fa0a159b7073e39dd88f527a55d1f35e8986a3c560f202a75bdb8d584 boost_1_76_0_b1.tar.gz eb098d6d5352e10b17a3c49d2927ed61f09b6544f7c534627de35dfa2560fe20 boost_1_76_0_b1.tar.bz2 For details of what's in the release, see <https://www.boost.org/users/history/version_1_76_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.76.0 Beta 1 Release Candidate 2
by Marshall Clow 13 Mar '21

13 Mar '21

The second release candidates for the 1.76.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/> The SHA256 checksums are as follows: c32edd34f767dd4bb67b86f76ebf58cf76822a5993a9b434c028b2dd08cfeefc boost_1_76_0_b1_rc2.zip eb098d6d5352e10b17a3c49d2927ed61f09b6544f7c534627de35dfa2560fe20 boost_1_76_0_b1_rc2.tar.bz2 39eecd9672e78b95c8e3fdec1430a63788d528a66d3c8799c4639238e5d785bd boost_1_76_0_b1_rc2.7z 3ec1f92fa0a159b7073e39dd88f527a55d1f35e8986a3c560f202a75bdb8d584 boost_1_76_0_b1_rc2.tar.gz The only changes from RC1 is an update to Boost.Interprocess, which was failing to compile on Mac OS X. As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

3 3

[release] Boost 1.76.0 Beta 1 Release Candidate 1
by Marshall Clow 11 Mar '21

11 Mar '21

The first release candidates for the 1.76.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/> The SHA256 checksums are as follows: a222d325cd3c9f66951ec9026eca6ff6f48dd563c9a025911d598d2aca8770ce boost_1_76_0_b1_rc1.tar.bz2 6b90b510a3de38fc30a071ac798da37545fb60a1d6b21aed1130b47c9c598977 boost_1_76_0_b1_rc1.zip b01627bd9ce934b092037da81696bb4482a44e6a31c8791dbed82eafe04b69fa boost_1_76_0_b1_rc1.tar.gz dbef57adbab1d4395d14000f0a2420fc82f87476e10d48359ceff7125a74b77a boost_1_76_0_b1_rc1.7z As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

1 3

(no subject)
by Jinlong Shen 11 Mar '21

11 Mar '21

Dear Madam/Sir, I used the boost::statechart asynchronous_state_machine to create a simple state machine. The state machine, the events and states are regular classes and are not class templates. Everything builds and works well on linux and qnx platform. However, on windows I got message that the the initial state is undefined. I think I have dealt with forward declaration well since it is build on linux and qnx. On Windows microsoft this compiler is used: Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24215.1 for x64 The error message is like this. (ClCompile target) -> C:\Program Files\boost_1_64_0\boost/statechart/state_machine.hpp(701): error C2027: use of undefined type 'xxxx::FirstState' C:\Program Files\boost_1_64_0\boost/statechart/state_machine.hpp(701): error C3861: 'initial_deep_construct': identifier not found Any hint how it could be wrong with Microsoft C++? Best regards,Jinlong Shen

2 1

Boost accepted in Google Summer of Code 2021
by David Bellot 09 Mar '21

09 Mar '21

We're in again! https://github.com/boostorg/wiki/wiki/Google-Summer-of-Code%3A-2021 David

1 0

MSM and multithreading. Not clear what pattern to follow.
by Andrea Fiorito 08 Mar '21

08 Mar '21

Hi, I'm trying to use MSM to implement a client server component for my app. The client is broadcasting a msg, that servers in a local network will detect and respond. The client at that point will connect to one of the servers and interact following the network protocol. For the network and threading I'm using boost ASIO. I have 2 submachines that manage one the discovering part, and the other the connection and dialogue with one server part. I found that would be beneficial to run the submachines in one thread managed by an io_context, with the idea of stopping that context to cancel all the asynchronous operations. Unfortunately there are some weird behaviours with submachines, and not getting if I missed the right way of doing things or else. the description of my last stopper is here: https://github.com/boostorg/msm/issues/37 Is anyone able to point me on the right direction? Regards, Andrea

2 1

CMake's PCH support and boost.test linker error
by Olaf Peter 04 Mar '21

04 Mar '21

Hello Boost users I have here a strange problem which occurs only if I try to build with precompiled headers using CMake. I've configured the project for use with dynamically linking. The error is: /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/10/../../../../lib64/crt1.o: in function `_start': (.text+0x24): undefined reference to `main' Something obvious? Thanks in advance The project's reduce is: ---8<--- test_driver.cpp --- 8< ---- #defineBOOST_TEST_MODULE "My Test Suite" #include<boost/test/unit_test.hpp> --->8------>8------>8--- ---8<--- test_x.cpp --- 8< ---- #include<boost/test/unit_test.hpp> .... --->8------>8------>8--- ---8<--- src/CMakeLists.txt --- 8< ---- ... set_source_files_properties(src/test_xxx.cpp APPEND PROPERTIES COMPILE_DEFINITIONS "BOOST_TEST_DYN_LINK" ) .... --->8------>8------>8------>8------>8------>8--- ---8<--- pch.pp --- 8< ---- #pragma once #include<boost/test/unit_test.hpp> --->8------>8------>8---

1 2

How should a "using zlib ..." jam statement look, for Boost to link to ZLib in the form of SO filename (libz.so) instead of by -lz?
by Bob 03 Mar '21

03 Mar '21

Hello Boost mailing list, I am building a code project in my user home directory on OpenBSD, and doing this involves both a local build of Boost and also a local build of ZLib. I do the whole build using GCC. This is a relatively ordinary build use case, however GCC on OpenBSD (at least in its current version) has a peculiarity to it, which is that it adds to LD the argument "-L/usr/lib" in the leading position, and this means that LD's search for libz.so will find and use the operating system's bundled ZLib binary which is /usr/lib/libz.so ALWAYS, and NEVER use my local libz.so . Can you help me understand if Boost can be customized to link to ZLib in the following way: I can force GCC/LD to use a particular libz.so file, by specifying it by filename, e.g. "gcc ... libz.so ...", "gcc ... /my/dir/libz.so ...", instead of by the conventional "-lz". Boost's build process is hardwired to "-lz" and I ask you to help me understand if there is a way to circumvent that. ZLIB_LIBRARY_PATH will not make "-lz" hit anything else than /usr/lib/libz.so , per the compiler's default -L/usr/lib in leading position, so it will not be of help to solve my problem. To my best awareness ZLIB_INCLUDE has nothing to do with linking, so it will not be of help to solve my problem. ZLIB_NAME would only be to customize the library name would it e.g. to "-lmycustomz", or what is it for? Please clarify so I could figure if it could be of help, though ideally i keep my local ZLib having its default name "libz.so". And this brings me to the path of solving the problem that I imagine could work, but that I don't understand fully from the Boost documentation: There is the possibility to customize ZLib build settings through the JAM configuration, that is user-config.jam . The syntax used is "using zlib ...". Can you please help me understand if this route works, if so how would that "using zlib ..." statement look, such that Boost's build process will NOT build ZLib itself, and then will NOT link to it via "-lz", but will instead link to it by "$MYCUSTOMBUILDDIR/libz.so"?

1 0

Boost.Python + `RecursionError` during deallocation
by Andrew Jones 01 Mar '21

01 Mar '21

Hi, I just raised the following issue on the Python issue tracker: https://bugs.python.org/issue43351 But I'm sharing it here to widen the net ... Basically, when moving from Python 2.7.14 to Python 3.7.5, and when using Boost.Python (Boost version 1.6.9), I'm seeing a crash in finalisation due to: ``` Exception ignored in: <Boost.Python.life_support object at 0x2acf473c5d10> RecursionError: maximum recursion depth exceeded while calling a Python object Fatal Python error: Cannot recover from stack overflow. ``` Everything else with the Python that's running, and the Boost.Python interface, is consistent between 2.7.14 and 3.7.5 -- it is just the Python version that's changing. I should say, Python 3.7.5 does otherwise seem operable, it just falls over when running this certain code (which just walks a linked-list of ~1400 elements via Boost.Python). Has anyone seen anything like this before? Does this list feel this is more likely a Python-proper issue, or a Boost.Python issue? Cheers, Andrew

1 0