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

Re: [Boost-users] Boost.DLL on MacOS (Intel) building Universal Binary ?
by Bo Zhou 18 Mar '23

18 Mar '23

It might not be the issue on Boost but macOS, the*.dylib file to be signed if you want it to run it as distribution. https://developer.apple.com/library/archive/documentation/Security/Conceptu… On Sat, Mar 18, 2023 at 12:49 PM Nicholas Yue via Boost-users < boost-users(a)lists.boost.org> wrote: > Hi, > > I have an application which uses Boost.DLL > > I have built and run them successfully on Linux, Windows and MacOS. > > I have an Intel Mac running Big Sur and have built Boost 1.81.0 > successfully as a universal binary with both arm64 and x86_64 libraries > combined. > > However, while other parts of boost library runs fine, I have found that > Boost.DLL will fail to load the plugins (also built as universal binary). > > Is there additional steps we need to take when building DLL plugins via > Boost.DLL as universal binary so that the loading mechanism is able to pick > the correct portion of the *.dylib that is for the current architecture of > the host application ? > > Cheers > -- > Nicholas Yue > https://www.linkedin.com/in/nicholasyue/ > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

Boost.DLL on MacOS (Intel) building Universal Binary ?
by Nicholas Yue 18 Mar '23

18 Mar '23

Hi, I have an application which uses Boost.DLL I have built and run them successfully on Linux, Windows and MacOS. I have an Intel Mac running Big Sur and have built Boost 1.81.0 successfully as a universal binary with both arm64 and x86_64 libraries combined. However, while other parts of boost library runs fine, I have found that Boost.DLL will fail to load the plugins (also built as universal binary). Is there additional steps we need to take when building DLL plugins via Boost.DLL as universal binary so that the loading mechanism is able to pick the correct portion of the *.dylib that is for the current architecture of the host application ? Cheers -- Nicholas Yue https://www.linkedin.com/in/nicholasyue/

1 0

New video: Getting Started with Boost.Asio: Timers and Serial Ports
by Richard 15 Mar '23

15 Mar '23

Utah Cpp Programmers has released a new video Getting Started with Boost.Asio: Timers and Serial Ports <https://www.youtube.com/watch?v=XB3uEit5R_Y> I/O operations are inherently asynchronous -- we don't know when input will arrive and when output will be generated. Network I/O can be particularly bothersome because of the long delays between sending a request and obtaining the response. Boost.Asio is a cross-platform C++ library for network and low-level I/O programming that provides developers with a consistent asynchronous model using a modern C++ approach. Boost.Asio covers timers, serial ports, files, pipes and TCP/IP networking. This month, Richard Thomson will give us an introduction to Boost.Asio concepts and asynchronous programming with this library. We'll look at how to use timers to notify our application of time passing and how to talk to serial ports asynchronously. Other Utah Cpp Programmers videos: <https://www.youtube.com/@UtahCppProgrammers> -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Terminals Wiki <http://terminals-wiki.org> The Computer Graphics Museum <http://ComputerGraphicsMuseum.org> Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>

1 0

[release] Boost 1.82.0 beta 1 released
by Marshall Clow 15 Mar '23

15 Mar '23

Boost release 1.82.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.82.0.beta1/source/ The SHA256 checksums are: efe17bea3f0b2c11f34828f37d5777f30eb6fef57af355c6a6664b08a4339999 boost_1_82_0_b1.7z 0af2a60f76abb4f411b1bd9c1a553f64454d9414990e8cc12f02f3b431e2ac45 boost_1_82_0_b1.tar.gz 495b2ae2f6970ea1e635f80222d9f6978148496cdd163e87c37cdd6de3b5ccfc boost_1_82_0_b1.zip edf4cb9e8e5a14412b91311438478ef6ce12afe2a54714eb2f0632a454c3d8d5 boost_1_82_0_b1.tar.bz2 Release notes (still need updates): https://www.boost.org/users/history/version_1_82_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

ASIO: Support for SQPOLL in io_uring backend
by Cyan Reddish 15 Mar '23

15 Mar '23

Hi. I was wondering if anything like that is planned. I am also interested in other general io_uring options like setting affinity masks for IO worker threads.

1 0

Boost Asio help
by Richard, Charles 01 Mar '23

01 Mar '23

Hi, I've been tasked with trying to figure out why we are getting an error in our log file, the error is "error: End of file". I'm still fairly new to doing real-world C++ development and I struggle with understanding why the code does what it does. The errors in our log file specifically are: 2023.02.20 08:45:49.470[UTC] [19626:140486796130176] TRACE - Process::CmdRunner::AsyncReadStdout<0x7fc594013b20> len = 0 2023.02.20 08:45:49.470[UTC] [19626:140486796130176] TRACE - Process::CmdRunner::AsyncReadStdout<0x7fc594013b20> error: End of file At a high level, my understanding is that we use Boost Asio to run python scripts where our C++ process will fork a new child process to run these python scripts. What I don't understand is why the code we have like the below was chosen to implement that functionality and to handle error handling. I've looked at some Asio boost tutorials but I still have gaps between our implementation and the Boost Asio tutorials and documentation. I'm also wondering why the a_errCode == boost::asio::error::eof is not seemingly catching the end of file. The code in the method CmdRunner::AsyncReadStdout does the following: void CmdRunner::AsyncReadStdout(boost::system::error_code a_errCode, size_t a_readSize) { DoLOG(TRACE, "Process::CmdRunner::%s<%p> len = %zu", __func__, this, a_readSize); if ( a_errCode ) { DoLOG(TRACE, "Process::CmdRunner::%s<%p> error: %s", __func__, this, a_errCode.message().c_str()) } if ( a_readSize > 0 ) { DoLOG(TRACE, "Process::CmdRunner::%s<%p> - read this: %zu bytes", __func__, this, a_readSize) _stdoutBufList.Copy(_stdoutReadBuf, a_readSize); // Call user callback to push out bytes Daemon::Service::DispatchEvent([this]() { _cbHandler(_cbCtxt, false); }); } else if ( a_errCode == boost::asio::error::eof ) { // Read done, call user callback function! DoLOG(TRACE, "Process::CmdRunner::%s<%p> - Child process (%d) STDOUT reached EOF", __func__, this, _childPid) _cmdDone = _eofStdout = true; _procStdout->close(); _procStderr->close(); Daemon::Service::DispatchEvent([this]() { _cbHandler(_cbCtxt, true); }); } else { // Async-read more, until EOF seen _procStdout->async_read_some(boost::asio::buffer(_stdoutReadBuf, PROC_READ_BUF_SIZE), [this](boost::system::error_code ec, std::size_t a_readSize) { AsyncReadStdout(ec, a_readSize); }); } } Any hints or specific links to look at to further clarify my understanding would be appreciated. Thanks! Chach Internal Use - Confidential

1 0

Precompiled Windows ARM/ARM64 binaries
by Stephan Brunner 01 Mar '23

01 Mar '23

Hi, are there any plans to ship precompiled windows binaries for ARM and/or ARM64 at some time on SourceForge [1]? Currently only a x86 and a x64 build is available there. If not, I'll look into building my own version for those architectures. Thanks a lot! [1] https://sourceforge.net/projects/boost/files/boost-binaries/1.81.0/ -- Mit freundlichen Grüßen / Best regards Stephan Brunner, M.Sc. Matrix: @boomer41:boomer41.net PGP: 5FB325E81E548282D458A65114A30C9CE3AE4CE2

1 0

Boost Libraries and Dropping C++ Language Support
by Glen Fernandes 23 Feb '23

23 Feb '23

*Boost library authors and maintainers are free to drop support for old C++ standards in their libraries, at any time. * This includes libraries that other Boost libraries depend on. It even includes core libraries like Boost.Core or Boost.Static_Assert. We ask that maintainers do the right thing by all our users (which may include other Boost libraries) by announcing a future breakage *at least two Boost releases in advance*. When that eventual release time arrives, if Boost libraries are broken in older standards modes due to another Boost library dropping support, it will not block the Boost release. This means that we do not need to announce "Boost is dropping C++03" because Boost doesn't "support C++03" now as it is. It means that you, maintainer of Boost.X, should realize that you are free to announce that "Boost.X is dropping C++XY in version 1.Z" as you see fit. Boost in its infancy thrived because its libraries were on the cutting edge. Boost libraries today should similarly not be confined simply because other Boost libraries have chosen to depend on them. Furthermore, as Boost release managers we support authors exercising this freedom, and do not intend to impose any restrictions on what language support they must maintain. We will add a page to the Boost website stating the above formally. -- The release team (Glen Fernandes, Marshall Clow)

2 1

[iostreams] When plan to move to C++20
by Seyyed Soroosh Hosseinalipour 17 Feb '23

17 Feb '23

ITNOA I have question about the plan to migrate code base from C++03 to C++20 for iostreams library I think iostreams library have very more clean if using modern C++ features, such as Concept Did you have any plan about that? thanks

4 5

Abwesenheitsnachricht: Re: [iostreams] When plan to move to C++20
by Sören Textor 17 Feb '23

17 Feb '23

Derzeit bin ich nicht im Hause Ihre E-Mail wird nicht weitergeleitet. In dringenden Fällen bitte support(a)ditec-gmbh.de oder Telefonhotline +49-6221-31698-110 oder die Zentrale +49-6221-31698-0 kontaktieren. Mit freundlichen Grüßen Dr. Sören Textor ----------------------------------------------- DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH Im Breitspiel 19 | 69126 Heidelberg | Germany Handelsregister | Mannheim | HRB 341229 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights.

1 0