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

boost::process v1 broken in 1_88_0
by Sebastian Koerner 29 May '25

29 May '25

Hi Boost-Users, I understand that boost process has v2 and v1 is deprecated, but I thought v1 will at least work on for existing stuff. Between 1_87 and 1_88 process v1 stopped working with v1 code. Something changed v1-incompatible with the includes, like: boost::process::child is unknown. error: ‘child’ is not a member of ‘boost::process’ 73 | std::vector<boost::process::child> m_processes; Is this known or easy-to fix?

2 1

[boost] [openmethod] Peer review conclusion
by Дмитрий Архипов 28 May '25

28 May '25

Dear Boost community, the formal review of candidate Boost.OpenMethod has taken place between 28th of April and May 7th. I have received 6 reviews in total. Four of the reviews recommended unconditional, and 1 conditional acceptance. One reviewer recommended to reject the library. The reviews came from: - Joaquin M López Muñoz, - Christian Mazakas, - Ruben Perez, - Yannick Le Goc, - Klemens Morgenstern, - Andrzej Krzemienski. Also, several people have given insightful comments but did not provide a review. I would like to thank all of the people who took their time to write reviews or participate in the discussions. Your effort was very important and valuable. The outcome of the review is that Boost.OpenMethod is ACCEPTED with some CONDITIONS. 1. The convenience header <boost/openmethod.hpp> should be changed to not introduce identifiers to the global namespace. Reviewers suggested several alternatives to that: either moving those global entities into an alternative header, or put them into a dedicated namespace which users could use via using namespace. 2. The library should not choose an arbitrary ambiguous overrider. Virtually all reviewers have expressed strong dislike for this behaviour. The default should be an error. More lax overrider selection may be provided as an option. 3. The library's documentation should be improved in several areas: * The concepts used by the documentation should be explained early on and more thoroughly. * The library should not claim to implement N2216, as it diverges from it significantly. Instead it may remark on being inspired by it. * Better explain potential platform-specific limitations of certain use cases (runtime loading of shared libraries) and error conditions. In addition, I want to discuss several criticisms that have been expressed during the review. One is that essentially the library doesn't solve a problem that is worth solving. That is, you never need an open set of types combined with an open set of operations. I believe that 10 years of library's use should mostly dispel such concerns. I personally have also encountered such a situation in my practice. The second criticism is that the flexibility of the library comes with higher chance of programmer error, as some usual safe guards go out the window. I can attest that in "many types, many operations" situations alternative approaches are comparably error-prone. It seems to me that this is largely inherent to the complexity of the problem. My advice to the author is to highlight dangerous situations, so that potential users can better evaluate if the added flexibility is worth it. Thanks to Jean-Louis Leroy for submitting this library to Boost. And thanks again to the reviewers and everyone who provided feedback, who ultimately made this review possible.

1 0

How to replace get_io_service()/get_io_context()-calls
by Klebsch, Mario 21 May '25

21 May '25

Hello, I have been using boost::asio for about a decade. I was using boost-1_63. I use get_io_service() (e.g. on a socket) to get a reference to the io_context, e.g. to post(…) on that io_context. I have read, that get_io_service() got deprecated and was removed. I now am facing, the challenge to find a replacement for get_io_service(). I found https://stackoverflow.com/a/39447000/6832488 suggesting to use get_executor().context() as a replacement for get_io_service(). And although the reference returned from get_executor().context() points to the same address as my io_context, it does have the wrong type. I cannot do socket.get_executor().context().post(…). I also found https://stackoverflow.com/a/67773642/6832488, suggesting to (C-Style)cast s to (boost::asio::io_context&). > #define GET_IO_SERVICE(s) ((boost::asio::io_context&)(s).get_executor().context()) But trying C++ (more or less) type safe to static_cast< boost::asio::io_context&>(s) fails to compile. I found that I misinterpreted > ((boost::asio::io_context&)(s).get_executor().context()) to cast (s) to ((boost::asio::io_context&). When I use > static_cast<boost::asio::io_service&>(s.get_executor().context()) My code finally compiles. I must admit, that I find the documentation of get_executor() quiet useless. Btw, Boost.org seems to be useless, too. When I try to read https://www.boost.org/doc/libs/1_63_0/doc/html/boost_asio/reference.html, I get > Error 503 first byte timeout. ☹ The documentation of basic_socket::get_io_service() in version 1_40_0 lists its signature as: > boost::asio::io_service & get_io_service(); That is useful, I can go to the documentation of boost::asio::io_service and find the methods usable on the io_service like post(). But for the current boost version 1_88_0, the signature of basic_stream_socket::get_executor() is documented as: > const executor_type & get_executor(); Ok, executor_type is documented as of basic_stream_socket::executor_type > typedef Executor executor_type; Executor is a template parameter. But when I look at ip::tcp::socket, I find: > typedef basic_stream_socket< tcp > socket; But basic_stream_socket is documented as > template< > typename Protocol, > typename Executor> > class basic_stream_socket : > public basic_socket< Protocol, Executor > Where the hell is the 2nd template parameter for basic_stream_socket? There is no default value of Executor, so how does the template instantiation of basic_stream_socket<tcp> compile? How am I supposed to find out, that I can invoke context() on the return value of get_executor()? I am totally screwed up with the documentation of current boost::asio. ☹ I hope, anybody on this mailing list can enlighten me. Many thanks in advance, Mario Klebsch Mario Funktion | R&D Tel: +49 (0) 531 38 701 718 Raum: Braunschweig, E20 Diese E-Mail und die an sie angehängten Dateien sind ausschließlich für Personen oder Institutionen bestimmt, deren Namen oben aufgeführt sind. Sie können Informationen enthalten, die durch das Berufsgeheimnis geschützt sind und deren Weitergabe strengstens untersagt ist. Jede elektronische Nachricht kann geändert werden. ACTIA lehnt jede Verantwortung für diese Nachricht ab. Der Inhalt dieser Nachricht stellt keine Verpflichtung seitens unseres Unternehmens dar. Wenn Sie kein Empfänger sind, weisen wir Sie darauf hin, dass das Lesen, Vervielfältigen oder Verteilen strengstens untersagt ist. Wir bitten Sie daher, uns umgehend über diesen Brief zu informieren und diese Nachricht sowie eventuell beigefügte Unterlagen aus Ihrem Postfach zu löschen. Danke. This e-mail and the files attached to it are intended exclusively for persons or institutions whose names are listed above. They may contain information that is protected by professional secrecy and the disclosure of which is strictly prohibited. Any electronic message can be modified. ACTIA declines all responsibility for this message. The content of this message does not represent a commitment on the part of our company. If you are not a recipient, we would like to point out that reading, copying or distribution is strictly prohibited. We therefore ask you to inform us immediately about this letter and to delete this message and any accompanying documents from your mailbox. Thank you.

2 1

Boost:1.82.0 ASIO changed its behavior
by Nedelin Rusev 21 May '25

21 May '25

Hi, Recently I inherited an old project, which uses boost 1.65.0 and ASIO, for custom implementation of the SCTP protocol. Technically it adapts the existing ASIO TCP for SCTP. Another implementation uses this ASIO-SCTP to asynchronously send and receive data. My task was to make both implementations work with any boost version from 1.65.0 to 1.87.0. I did the necessary changes and the project now compiles and runs, but I face a test deviation with boost versions 1.82.0 and above. The test is more or less simple: - we have pre-generated data - we start a server, which only receives data and stores it in file per connected client - we start multiple clients, each running in its own thread. Each client sends its own data to the server at a random moment - finally we check if the server has received the same data as the clients have sent. With boost versions up to 1.81.0 the test passes OK. But with boost version 1.82.0 we observe wrong order of the data stored by the server. To illustrate it roughly: Client sends: 0,1,2 Server stores: 0,2,1 (0 is OK, Next we should have 1, but we get 2). Note: the real test data is hundreds of bytes long, not single digits. Note: the test seems to have issues, but on the particular machine, the behavior is consistent: test is OK with boost 1.81.0 and NOK with boost 1.82.0 I suspect the problem has something to do with the "on_immediate()" extension, introduced in boost 1.82.0. Somehow it speeds up the client threads execution and changes the order of the sent data. I failed to find any similar problems, reported in internet (git, boost forums, etc) I have enabled BOOST_ASIO_ENABLE_HANDLER_TRACKING and, if I get the log right, client threads are executed faster. I have attached the handler tracking logs for boost versions 1.81.0 and 1.82.0. My question is how to keep the old code behavior (pre 1.82.0) with later versions? Is there any way to disable the "on_immediate()" functionality? Are there any guidelines for using later versions of boost ASIO (1.82.0 and later)? Providing a simplified example test is hard, as the code-base is quite large. I will try to make something up, but this will take time. Thank you!

2 1

Issues with boost executor_work_guard
by João Fernando Silva 22 Apr '25

22 Apr '25

Hello all, We are facing some issues with boost::asio::executor_work_guard. We are spawning some threads which are bound to a boost::asio::io_context and proteced by a boost::asio::executor_work_guard so that they do not exit even if there is no work to be done. However, despite the work_guard still being valid, we see that the threads exit because boost::asio::detail::scheduler::outstanding_work reaches 0. All operations added to the queue are posted asynchronously. The boost version in use is 1.75 (also tested with 1.78 and the behaviour is the same). Could you help us on the following topics so that we can understand what the root cause may be? 1 - We created an implementation to track the number of elements on boost::asio::detail::op_queue, is this implementation valid? uint32_t size() { auto tmp_op = front_; uint32_t size{0}; while (tmp_op != 0) { ++size; tmp_op = op_queue_access::next(tmp_op); } return size; } 2 - Assuming the approach above is correct, we are trying to compare the values of outstanding_work with the returned value of op_queue.size(). However, these values do not seem to correlate, is this to be expected? 3 - Was this issue observed by someone else? If so what were the root causes? Thanks! Kind Regards, João Silva The information in this communication may contain confidential or legally privileged information. It is intended solely for the use of the individual or entity it addresses and others authorized to receive it. If you are not an intended recipient, you are hereby notified that any disclosure, copying, distribution or action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication by error, please notify us immediately by responding to this e-mail and then delete it from your system. Critical TechWorks is not liable for the proper and complete transmission of the information in this communication nor for any delay in its receipt This e-mail is environmentally friendly, just like Critical TechWorks, which lives in a paper-free atmosphere. Therefore, please consider the environment before printing it!

3 5

boost.parser parse int or double?
by kila suelika 12 Apr '25

12 Apr '25

``` #include <boost/parser/parser.hpp> #include <iostream> #include <string> #include <variant> namespace bp = boost::parser; auto numeric_parser = bp::int_ | bp::double_; //auto numeric_parser = bp::double_ | bp::int_; void parse_number(const std::string& input) { auto result = bp::parse(input, numeric_parser); if (result) { std::visit([](auto&& arg) { using T = std::decay_t<decltype(arg)>; if constexpr (std::is_same_v<T, int>) std::cout << "Integer: " << arg << std::endl; else if constexpr (std::is_same_v<T, double>) std::cout << "double: " << arg << std::endl; }, *result); } else { std::cout << "Parsing failed:" << " (" << input << ")" << std::endl; } } int main() { parse_number("24"); parse_number("24.3"); return 0; } ``` Above code failed to parse "24.3" which makes me confused. First int should failed but why it didn't match double? If use ``` auto numeric_parser = bp::double_ | bp::int_; ``` then all number parsed to double.

2 1

[release] Boost 1.88.0
by Marshall Clow 11 Apr '25

11 Apr '25

Release 1.88.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. The release contains two new libraries: * Hash2: An extensible hashing framework, from Peter Dimov and Christian Mazakas. * MQTT5: MQTT5 client library built on top of Boost.Asio, from Ivica Siladić, Bruno Iljazović, and Korina Šimičević. as well as numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.88.0> You can also download directly from: <https://archives.boost.io/release/1.88.0/source/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. -- The Boost Release Team Marshall Clow, Glen Fernandes, Ion Ion Gaztañaga

3 2

[boost] [OpenMethod] Boost.OpenMethod review scheduled
by Дмитрий Архипов 11 Apr '25

11 Apr '25

The review for the proposed Boost.OpenMethod library by Jean-Louis Leroy is scheduled to take place from April 28 to May 07. OpenMethods solve the Expression Problem by making it possible to define free virtual functions, i.e. virtual functions that exist outside of a class The library repository is here: https://github.com/jll63/Boost.OpenMethod. The documentation is here: https://jll63.github.io/Boost.OpenMethod.

1 0

Re: [Boost-users] JSON Schema support in C++ with boost::json?
by Alex 08 Apr '25

08 Apr '25

> 3. Generate validation code that can emit informative messages about failed validation. Valijson ( https://github.com/tristanpenman/valijson ) apparently supports Boost.Json for schema validation, although I haven't used it personally. Most C++ implementations of schema validation don't support a lot of the newer JSON schema versions. You could take a look at some of the C++ tools at https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupB… Regards, Alex Simpson

1 0

JSON Schema support in C++ with boost::json?
by Nigel Stewart 07 Apr '25

07 Apr '25

Hello all, There are a couple of things I'd like to do with JSON Schema in C++, which are similar to protobuf, but JSON-centric. 1. Generate a C++17 struct from a JSON Schema, names, types, optionality, nested data, arrays. 2. Generate C++17 code for serialising to/from the natve C++17 struct. 3. Generate validation code that can emit informative messages about failed validation. Seems to me this problem isn't specific to our application stack. Essentially we want to pass state between NodeJS and core C++ modules and have those interfaces evolve over time in a maintainable way. What's out there? - Nigel Stewart

3 3

Passing -D options with b2 to ASIO when compiling with mingw64 ucrt64?
by Joost Kraaijeveld 25 Mar '25

25 Mar '25

Hi, I try to compile Boost with MingW64 with ucrt64. I get warnings saying I should define _WIN32_WINNT with 0x0601 or higher and an error saying I must define USE_W32_SOCKETS. Is it possible to pass these on a command line to b2 or otherwise, without interfering with Boost's source? TIA -- Groeten, Joost

1 0

Re: [Boost-users] Boost-users Digest, Vol 5755, Issue 1
by Label 18 Mar '25

18 Mar '25

Hello, > Date: Mon, 17 Mar 2025 21:02:09 +0100 > From: Joost Kraaijeveld <J.Kraaijeveld(a)Askesis.nl> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Passing -D options with b2 to ASIO when > compiling with mingw64 ucrt64? > Message-ID: > <dc4a6232934d0d77af53a3054afddbc5b22a8bc1.camel(a)Askesis.nl> > Content-Type: text/plain; charset="UTF-8" > > Hi, > > I try to compile Boost with MingW64 with ucrt64. I get warnings saying > I should define _WIN32_WINNT with 0x0601 or higher and an error saying > I must define USE_W32_SOCKETS. > > Is it possible to pass these on a command line to b2 or otherwise, > without interfering with Boost's source? > > TIA > you can append the following definitions to the b2 command line: b2 ... define=_WIN32_WINNT=0x0A00 define=BOOST_USE_WINAPI_VERSION=0x0A00 I do not know whether USE_W32_SOCKETS needs only be defined or wants a special value, you can try define=USE_W32_SOCKETS or define=USE_W32_SOCKETS=1 -- __________________________________ Freundliche Grüße * Best regards * Met vriendelijke groeten * Meilleures salutations * Atentamente * Saludos Holger Gerth EB-Soft GmbH Neckargartacher Strasse 114 74080 Heilbronn Germany Tel: +49 7131-94660 Fax: +49 7131-10990 E-Mail: holger.gerth(a)eb-soft.de Web: https://www.ebsoft.de Amtsgericht-Registergericht-Stuttgart HRB 102882 Geschäftsführerin: Hannelore Sigler

1 0

release] Boost 1.88.0 beta 1 released
by Marshall Clow 16 Mar '25

16 Mar '25

Boost release 1.88.0 beta 1 is now available at: https://archives.boost.io/beta/1.88.0.beta1/source/ The SHA256 checksums are: bc4948bc664fde0c2142badae2679a42124b464dc58019250afe0ef57fd7763e boost_1_88_0_rc1.zip 3c334a9a743b68a35452b0223be8932fb39f26a6938382f9b9e625c4df99602c boost_1_88_0_rc1.tar.gz 9e42c0611500151d795d66a07ef0a21036c02d24678e2e887caf6d97fcbc25ca boost_1_88_0_rc1.tar.bz2 7faf60c4cb12ee90270e41716cf3735a8739016d7346983ce9f5e899e510b26d boost_1_88_0_rc1.7z Release notes (still need updates): https://www.boost.org/users/history/version_1_88_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

1 0

boost::json question
by Keeling, William 12 Feb '25

12 Feb '25

json::value RCamCfg::GetCfgValue(const std::string& key) { try {return config_.at_pointer(key);} catch(...) { json::value x; return x;} } bool RCamCfg::SetCfgValue(const std::string& key, const json::value& val) { try {config_.set_at_pointer(key, val);} catch(...) {return false;} return {true}; } The first function compiles and runs but the second fails to compile with the following: error: 'class boost::json::value' has no member named 'set_at_pointer'; did you mean 'at_pointer'? config_is defined as "json::value config_;" Any ideas what I am doing wrong? Thanks William Keeling

3 4

Newbie - Using Boost ASIO and Boost Thread from CMake based project
by Russell Haley 11 Feb '25

11 Feb '25

Hello, I am implementing a serial port protocol in a Linux based library. We build boost ourselves (1.86.0) for inclusion in thrift so I am trying to use as much as I can just from the Boost libraries to gain some experience with them. My serial port driver is using the serial_port class from Boost ASIO. It's super cool and working well. To include Boost ASIO in my CMake target, all I have done is this: cmake_minimum_required(VERSION 3.30) set(CMAKE_CXX_STANDARD 20) set(BOOST_ROOT "${PROJECT_SOURCE_DIR}/../dataman_service/boost-install-x86_64-Debug/") find_package(Boost CONFIG) #This is an alternate use? #find_package(Boost NO_MODULE) add_library(L2PUtility L2Packet.cpp L1Transport.cpp crc1021.cpp) target_include_directories(L2PUtility PUBLIC ${CMAKE_SOURCE_DIR} ${BOOST_ROOT}/include) Note there is no target_link_libraries, but ASIO works. I thought that was because it's an HPP/Header only implementation? Since I need to add some threading to the project, I thought I would use the boost_thread library. Examples online show the inclusion of boost/thread.hpp, so I assumed it is another header only implementation and no link library is needed but I am getting a linking error: [2/4] Linking CXX executable L2PSecondary FAILED: L2PSecondary : && /usr/bin/c++ -g CMakeFiles/L2PSecondary.dir/main.cpp.o -o L2PSecondary libL2PUtility.a && : /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): warning: relocation against `_ZTVN5boost6detail16thread_data_baseE' in read-only section `.text._ZN5boost6detail16thread_data_baseC2Ev[_ZN5boost6detail16thread_data_baseC5Ev]' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `L1Transport::start_detached()': /home/rhaley/tuleap/BoostAsioL2p/L1Transport.cpp:440:(.text+0x1b32): undefined reference to `boost::thread::detach()' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `boost::detail::thread_data_base::thread_data_base()': /home/rhaley/tuleap/BoostAsioL2p/../stroma_dataman_service/boost-install-x86_64-Debug/include/boost/thread/pthread/thread_data.hpp:162:(.text._ZN5boost6detail16thread_data_baseC2Ev[_ZN5boost6detail16thread_data_baseC5Ev]+0x24): undefined reference to `vtable for boost::detail::thread_data_base' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `boost::thread::start_thread()': /home/rhaley/tuleap/BoostAsioL2p/../stroma_dataman_service/boost-install-x86_64-Debug/include/boost/thread/detail/thread.hpp:182:(.text._ZN5boost6thread12start_threadEv[_ZN5boost6thread12start_threadEv]+0x28): undefined reference to `boost::thread::start_thread_noexcept()' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `boost::thread::~thread()': /home/rhaley/tuleap/BoostAsioL2p/../stroma_dataman_service/boost-install-x86_64-Debug/include/boost/thread/detail/thread.hpp:257:(.text._ZN5boost6threadD2Ev[_ZN5boost6threadD5Ev]+0x18): undefined reference to `boost::thread::detach()' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `boost::thread::get_id() const': /home/rhaley/tuleap/BoostAsioL2p/../stroma_dataman_service/boost-install-x86_64-Debug/include/boost/thread/detail/thread.hpp:738:(.text._ZNK5boost6thread6get_idEv[_ZNK5boost6thread6get_idEv]+0x27): undefined reference to `boost::thread::native_handle()' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `boost::thread::join()': /home/rhaley/tuleap/BoostAsioL2p/../stroma_dataman_service/boost-install-x86_64-Debug/include/boost/thread/detail/thread.hpp:762:(.text._ZN5boost6thread4joinEv[_ZN5boost6thread4joinEv]+0x90): undefined reference to `boost::thread::join_noexcept()' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o): in function `boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf<void (L1Transport::*)(), void, L1Transport>, boost::_bi::list<boost::_bi::value<L1Transport*> > > >::~thread_data()': /home/rhaley/tuleap/BoostAsioL2p/../stroma_dataman_service/boost-install-x86_64-Debug/include/boost/thread/detail/thread.hpp:94:(.text._ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi2mfIM11L1TransportFvvEvS6_JEEENS2_4listIJNS2_5valueIPS6_EEEEEEEED2Ev[_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi2mfIM11L1TransportFvvEvS6_JEEENS2_4listIJNS2_5valueIPS6_EEEEEEEED5Ev]+0x26): undefined reference to `boost::detail::thread_data_base::~thread_data_base()' /usr/bin/ld: libL2PUtility.a(L1Transport.cpp.o):(.data.rel.ro._ZTIN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi2mfIM11L1TransportFvvEvS6_JEEENS2_4listIJNS2_5valueIPS6_EEEEEEEEE[_ZTIN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi2mfIM11L1TransportFvvEvS6_JEEENS2_4listIJNS2_5valueIPS6_EEEEEEEEE]+0x10): undefined reference to `typeinfo for boost::detail::thread_data_base' /usr/bin/ld: warning: creating DT_TEXTREL in a PIE collect2: error: ld returned 1 exit status I tried adding a target_link_library: target_link_libraries(L2PUtility PUBLIC boost_thread) To no avail. I now get a missing library in the EXECUTABLE, not in the library that actually includes boost_thread! Does that mean it found it for the L2Utility library? (so confused...) Here is my executable target: add_executable(L2PSecondary main.cpp) target_include_directories(L2PSecondary PRIVATE ${CMAKE_SOURCE_DIR} ${BOOST_ROOT}/include) target_link_libraries(L2PSecondary PRIVATE L2PUtility) And here is the linking error: [1/2] Linking CXX executable L2PSecondary FAILED: L2PSecondary : && /usr/bin/c++ -g CMakeFiles/L2PSecondary.dir/main.cpp.o -o L2PSecondary libL2PUtility.a -lboost_thread && : /usr/bin/ld: cannot find -lboost_thread: No such file or directory collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. I confirmed that my boost installation has the library libboost_tread.a. rhaley@linuxdev2:~/tuleap/dataman_service/boost-install-x86_64-Debug$ find . -iname "*thread*.a" ./lib/libboost_thread.a Adding link libraries to the executable targets doesn't fix anything. Can anyone point out what I am doing wrong? Thanks in advance, Russ

1 0

special character handling problem
by budhirajakush7＠gmail.com 30 Jan '25

30 Jan '25

hi everyone i have a problem while passing flag with a space it gets break this is my jamroot snippet my_var = "Nov 30 2024" ; my_var2 = $(PVK_ACCESSDATE_LONG) ; ECHO "$(my_var2)" ; ECHO "$(my_var)" ; if $(PROTOCOL) = common { c_flags = $(CXXFLAGS) ; c_flags += -DPVK_ACCESSDATE_LONG="\"\\\"$(my_var2)\\\"\"" ; c_flags += -DPVK_ACCESSDATE_LONG="\"\\\$(my_var)\\\"\"" ; } both my_var and my_var2 are echoing the same thing but when passing to flags they get break here is the log Nov 30 2024 Nov 30 2024 c_flags: -DPVK_VTL_VERSION="\"24.2\"" c_flags: -DPVK_ACCESSDATE_LONG="\"Nov\"" c_flags: -DPVK_ACCESSDATE_LONG="\"30\"" c_flags: -DPVK_ACCESSDATE_LONG="\"2024\"" c_flags: -DPVK_ACCESSDATE_LONG="\Nov 30 2024\"" c_flags: -DPVK_BASE_VERSION="\"24.2\"" c_flags: Someone please help

1 0

"error: Unable to find file or target named" when using BCP to change Boost namespace
by Nicholas Williams 17 Jan '25

17 Jan '25

Background: My organization uses Boost internally for one of its software products, which is itself a C++ library. Users of our library also often use Boost. As such, we must compile our Boost in a different namespace so that the Boost symbols loaded when our library loads do not interfere with whatever different-version Boost symbols our users might load. Historically, another member of the team has been responsible for building new versions of Boost, but now it's me. I am doing this the same way our code/documentation has previously done it, but it is no longer working, and the errors I'm receiving are not familiar to the team member who was previously responsible for this. The last time we built a new Boost version was 1.80.0. I am now doing it with 1.87.0. The example: Further below, I include a lot of information and build commands, but that might not be useful to you. To help, I have created a minimal reproduction program for reproducing the error. You can clone and use it here: https://github.com/beamerblvd/unable-find-target-with-boost-bcp The good: With minimal effort and using our existing tools and configurations, I was easily able to bootstrap `b2` and then run `b2` to build stock Boost with the normal `boost` namespace. All of that worked perfectly and without error. The bad: When I went to do the same thing but with our custom namespace (via bcp), things fell apart. Our existing tooling copies the untouched 1.87.0 source tree into {dir}/_src. {dir}/user-config.jam is configured as follows: ``` constant BOOST_VERSION : mybranchname-1.87.0.a ; constant MY_PLATFORM : macos15-clang16-arm-d ; constant MY_LABEL : MYextralLabel ; constant BOOST_USER_CONFIG : <my_boost/config/user.hpp> ; using clang : 16 : clang++ : <cxxflags>-fvisibility=hidden <cxxflags>-fvisibility-inlines-hidden ; ``` Within {dir}/_src, I call `bootstrap.sh` and then build `bcp` with: bc -sBOOST_ROOT={dir}/_src \ --boost-build=tools/build/src \ cxxstd=20 \ -d \ 2 \ -j \ 2 \ -q \ --prefix={dir}/bcp \ --build-dir={dir}/bcp \ --stagedir={dir}/bcp/stage \ --user-config={dir}/user-config.jam \ --layout=system \ toolset=clang-darwin \ threading=multi \ link=shared \ architecture=arm \ instruction-set=nocona \ address-model=64 \ --without-python \ --disable-icu \ variant=release tools/bcp That takes a few minutes to complete and does so without error. Once `bcp` is built, I run it with: mkdir {dir}/_dst && \ {dir}/bcp/bin/bcp --boost={dir}/_src --namespace=boost_MYextralLabel --namespace-alias Jamroot boost boost-build.jam boostcpp.jam bootstrap.bat bootstrap.sh build status tools [insert_name_of_every_dir_in_libs] {dir}/_dst That takes a few minutes to complete and does so without error. The contents of {dir}/_dst look as I would expect them to look, with diffs against {dir}/_src reflecting the change in namespace. Once complete, I cd into {dir}/_dst, re-bootstrap, and run `b2` to compile the modified Boost: b2 -sBOOST_ROOT={dir}/_dst \ --boost-build=tools/build/src \ cxxstd=20 \ -d \ 2 \ -j \ 2 \ -q \ --prefix={dir} \ --build-dir={dir}/shobj \ --stagedir={dir}/stage \ --user-config={dir}/user-config.jam \ --layout=system \ toolset=clang-darwin \ threading=multi \ link=shared \ architecture=arm \ instruction-set=nocona \ address-model=64 \ --without-python \ --disable-icu \ variant=debug This fails quickly, here: ... - native syslog supported : yes [2] - pthread supports robust mutexes : no [2] - Boost.Regex is header-only : yes [2] error: Unable to find file or target named error: '/boost/align//boost_align' error: referred to from project at error: '{dir}/_dst/libs/atomic/build' make: *** [build] Error 1 I have tried dozens of different things over the past two days and can't remember most of them, but they didn't change the outcome, so I don't supposed they're relevant. The one thing that *did* change the outcome is that, after running `bcp` and before re-bootstrapping in {dir}/_dst, I tried deleting the {dir}/_dst/boost directory. This still failed, but it got slightly further and failed with a different (albeit extremely similar) error: ... - std_wstreambuf : no [2] - std_wstreambuf : no [3] - BOOST_COMP_GNUC >= 4.3.0 : no [2] - BOOST_COMP_GNUC >= 4.3.0 : no [4] error: Unable to find file or target named error: 'libs/thread/build//boost_MYextralLabel_thread' error: referred to from project at error: '.' make: *** [build] Error 1 I feel like I've exhausted my ability to discern what the problem is. Other than updating a handful of compiler flags (like changing cxxstd=17 to cxxstd=20), I'm doing this the same way we have (allegedly) always done it, but it's not working anymore and I don't know why. I would appreciate any guidance you can offer. Thank you, Nick

2 6

"error: No best alternative for {dir}/libs/mpi/build/boost_mpi", but the build succeeds
by Nicholas Williams 17 Jan '25

17 Jan '25

I'm building the full stock, unmodified Boost 1.87.0. I have previously built Boost 1.80.0 without issue. After bootstrapping, when running `b2` to actually build Boost, I get the following "errors": ... - has stat::st_birthtimespec : yes [5] - has fdopendir(O_NOFOLLOW) : yes [5] - has dirent::d_type : yes [5] - has POSIX *at APIs : no [5] - has fallocate : no [5] - cxx11_static_assert : yes [5] error: No best alternative for {dir}/libs/mpi/build/boost_mpi with <abi>aapcs <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>mach-o <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <context-impl>fcontext <coverage>off <cxxstd-dialect>iso <cxxstd>20 <debug-symbols>off <exception-handling>on <extern-c-nothrow>off <inlining>full <instruction-set>nocona <known-warnings>hide <link>shared <optimization>speed <os>MACOSX <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.9 <rtti>on <runtime-debugging>off <runtime-link>shared <stdlib>native <strip>off <target-os>darwin <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>darwin <toolset-clang:version>14 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64 matched: (empty) matched: (empty) error: No best alternative for {dir}/libs/mpi/build/boost_mpi with <abi>aapcs <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>mach-o <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <coverage>off <cxxstd-dialect>iso <cxxstd>20 <debug-symbols>off <exception-handling>on <extern-c-nothrow>off <inlining>full <instruction-set>nocona <known-warnings>hide <link>shared <optimization>speed <os>MACOSX <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.9 <rtti>on <runtime-debugging>off <runtime-link>shared <stdlib>native <strip>off <target-os>darwin <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>darwin <toolset-clang:version>14 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64 matched: (empty) matched: (empty) - gcc visibility : yes [2] - cxx14_decltype_auto : yes [2] - cxx14_generic_lambdas : yes [2] ... I used scare quotes around "errors," because these errors do not appear to actually break anything. The build completes fully and successfully, and all the libraries are built as expected. It appears to be more of a warning than an error, but I don't love warnings either, so I'd like to solve it. The only relevant result I could find Googling about this was [this other mailing list message]( https://lists.boost.org/Archives/boost/2024/11/258275.php) which was a reply to "[release] Boost 1.87.0 Beta 2 Release Candidate is available," and to which nobody ever replied. Doesn't really clear anything up for me. FWIW, I get these "errors" on RHEL 8 GCC 8, 9 GCC 11, and 9 GCC 14; Ubuntu 20.04 GCC 9, 22.04 GCC 11, and 24.04 GCC 13; macOS 12 Clang 14 (Intel and ARM), 14 Clang 16 (Intel and ARM), and 15 Clang 16 (Intel and ARM); Windows 10 MSVC 2022 and 11 MSVR 2022; and Windows Server 2022 MSVC 2022 and 2025 MSVC 2022. Any insights or guidance would be appreciated. Thanks, Nick

2 4

ICU not found while building Boost
by Cory Riddell 13 Jan '25

13 Jan '25

I'm having trouble building Boost 1.87 on Windows using the latest VS2022. I'm starting from the "x64 Native Tools Command Prompt for VS 2022". I've downloaded the latest ICU binaries and updated my PATH, LIB, and INCLUDE environment variables: set PATH=%PATH%;D:\icu\bin64 set LIB=%LIB%;D:\icu\lib64 set INCLUDE=%INCLUDE%;D:\icu\include I go into my boost directory and run bootstrap.bat. It seems to complete, creating b2.exe. I then run "b2 address-model=64" and it's not finding icu: E:\boost_1_87_0>b2 address-model=64 Performing configuration checks - default address-model : 64-bit [1] - default architecture : x86 [1] Building the Boost C++ Libraries. warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam. note: to suppress this message, pass "--without-graph_parallel" to bjam. - icu : no [2] - iconv (libc) : no [2] - iconv (separate) : no [2] - cxx11_auto_declarations : yes [2] - cxx11_decltype : yes [2] I ctrl-c to quit at this point and looked at my config.log and it doesn't seem to find icu when building has_icu_test.obj: compile-c-c++ bin.v2\libs\locale\build\msvc-14.3\debug\x86_64\link-static\threading-multi\has_icu_test.obj has_icu_test.cpp E:\boost_1_87_0\libs\locale\build\has_icu_test.cpp(6): fatal error C1083: Cannot open include file: 'unicode/coll.h': No such file or directory The file D:\icu\include\unicode\coll.h does exist though. Is there some reason my environment variables don't make it to the processes kicked off by b2? Or am I overlooking something obvious? Any help is greatly appreciated. Cory

3 3

Generating a fully namespaced boost installation
by Janosch Machowinski 07 Jan '25

07 Jan '25

Hi, we ran into an issue, were the system installation of boost is exposed by a third party lib we rely on (ROS), but it contains a bug. The bug in boost is fixed in a way more recent version of boost, therefore we are looking into using two versions of boost at the same time. To archive this, we want to run the newer boost version in a custom namespace, and already found the bcp tool, that helps with generating a namespace version of boost for us. The issue we are now hitting is, that the includes in our custom boost version are not altered by bcp, and therefore pick up the system headers. E.g. geometry.hpp contains '#include <boost/geometry/geometry.hpp>' but in order to work for us, it would need to be '#include <our_boost/geometry/geometry.hpp>'. Are we missing some magical bcp option, or is this just not supported ? Thx Janosch -- Janosch Machowinski cellumation GmbH | Linzer Str.5 | 28359 Bremen | Germany P: +49 421 331135 35 F: +49 421 331135 99 J.Machowinski(a)cellumation.com Website | YouTube Registernummer: HRB32569 | Registergericht: Amtsgericht Bremen | Ust-Id.Nr.: DE313140406 Geschäftsführer: Dr.-Ing. Hendrik Thamer, Claudio Uriarte Diese E-Mail und alle damit übermittelten Dateien sind vertraulich und ausschließlich für die Verwendung durch die Person oder Gesellschaft, an die sie adressiert sind, bestimmt. Die Weitergabe sowie Vervielfältigung, Verwertung und Mitteilung des Inhalts der E-Mail sind nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung This e-mail and all files transmitted with it are confidential and intended exclusively for use by the person or company to whom they are addressed. The transmission, reproduction, exploitation and communication of the contents of the e-mail are only permitted with our express permission. All rights reserved, in particular in the event of an application for industrial property rights.

1 0

asio::strand: Order of execution
by Georg Gast 28 Dec '24

28 Dec '24

Hi, If I use a asio::strand and post() there multiple function objects, are they executed in the same order or is the order of execution not specified? I think to use it as a work queue but I need them to be processed in sequence... Thx Georg

1 0

[release] Boost 1.87.0
by Marshall Clow 12 Dec '24

12 Dec '24

Release 1.87.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraries: * Boost.Parser: A framework for building parsers, from Zach Laine. The release also contains numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.87.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.87.0/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. -- The Boost Release Team Marshall Clow, Glen Fernandes, Ion Gaztañaga

1 0

[release] Boost 1.87.0 beta 1 released
by Marshall Clow 16 Nov '24

16 Nov '24

Boost release 1.86.0 beta 1 is now available at: https://archives.boost.io/beta/1.87.0.beta1/source/ The SHA256 checksums are: 2e7cdf358526e8937b36b93fc96c501b8d6a0c8436e95e65440de31c48ec3086 boost_1_87_0_b1.tar.bz2 98a86940c13509dfd0288a3075280f46a76c9a3faeb8a9bf49ca7f9e6a271995 boost_1_87_0_b1.tar.gz 2ca4c019d0c96fd160dec5292a7a6bfcf7b4e592cd238a2207e17084f8021d08 boost_1_87_0_b1.zip 5ea32facd963dbb79ceb5bda7ef7546017ea5da854158f8933bbad74d6bbe622 boost_1_87_0_b1.7z This is slightly different than the RC3. Someone committed a documentation fix to master after we had started the release process, and rather than re-do the whole thing (and re-tag everything), we decided to go with the release that we prepared. The person who did this has been informed of the problems that he caused, and I don’t think he’ll do it again. Release notes (still need updates): https://www.boost.org/users/history/version_1_87_x.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

1 0

Unable to find boost atomic library header files//boost-1.84.0
by Pawan Badganchi 15 Oct '24

15 Oct '24

Hi, I am trying to resolve below error. Tried adding below path to atomic.cmake custom file but still failing with same issue. Could you please help here? include_directories( ${Boost_LIBRARY_DIRS}/atomic/test ) ERROR: Compilation failed Stdout: [ 50%] Building CXX object CMakeFiles/test_atomic.dir/atomicity.cpp.o Stderr: /sdk/sysroots/core2-64-poky-linux/usr/share/doc/boost-atomic/examples**/atomicity.cpp:38:10: fatal error: test_clock.hpp: No such file or directory 38 | #include "test_clock.hpp" | ^~~~~~~~~~~~~~~~ compilation terminated. make[2]: ***** [CMakeFiles/test_atomic.dir/build.make:76: CMakeFiles/test_atomic.dir/atomicity.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/test_atomic.dir/all] Error 2 make: *** [Makefile:91: all] Error 2 Returncode: Expected: 0 Actual: 2 Below is the my atomic.cmake file content. cmake_minimum_required(VERSION 2.8) FIND_PACKAGE(Boost REQUIRED COMPONENTS atomic ) FIND_PACKAGE(Boost REQUIRED COMPONENTS thread ) include_directories( ${Boost_LIBRARY_DIRS}/atomic/test ) add_executable(test_atomic atomicity.cpp ) target_link_libraries(test_atomic ${Boost_LIBRARIES} ) Thanks & Regards, Pawan KPIT Technologies,Pune This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

1 0

[boost] Boost.LEAF in Embedded Systems (CppCon)
by Vinnie Falco 23 Sep '24

23 Sep '24

At CppCon 2024 the C++ Alliance sponsored a program to interview conference goers about Boost-related topics. This is the first video in the series: Boost.LEAF in Embedded Systems: Insights from Ex-Google Engineer Khalil Estelle at CppCon https://www.youtube.com/shorts/BksBxnTLltY Enjoy! Thanks

1 0