- Boost-users - lists.boost.org

Re: [Boost-users] Boost-users Digest, Vol 5456, Issue 1
by philippe DALET 23 Feb '21

23 Feb '21

Hi, I have built some binaries for boost and python https://sourceforge.net/projects/pcpu/files/Boost/ boost 1.71 python3.7&numpy3.7 for ubuntu 20.04 64 bits boost 1.75 python3.789&numpy3.789 for visual studio 2019 mscv14.2 - win10 Ph.DALET Le mar. 23 févr. 2021 à 11:03, <boost-users-request(a)lists.boost.org> a écrit : > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. Re: Boost cannot find numpy37 on Dockerized Ubuntu 20.04 > (Roy de Bokx) > 2. Re: flyweights, nested flyweights and shared libraries > (Andreas Buykx) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 22 Feb 2021 15:49:11 +0100 > From: Roy de Bokx <rdebokx1990(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost cannot find numpy37 on Dockerized > Ubuntu 20.04 > Message-ID: > < > CAFLoxwXy8_an1jZh_PQMkjppbOWyixvR5Exw1DCeaUyV9xDfBA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Op vr 19 feb. 2021 om 22:05 schreef Nathan Ernst via Boost-users < > boost-users(a)lists.boost.org>: > > > The missing symbols you quoted come from python itself. It looks like > > you're missing a "-lpython" linker flag. > > > Thanks! That definitely put me on the right track. Eventually I got it > working using the "-lpython3.6m" flag, since I found that the Python3.6 .so > file was situated at /usr/lib/x86_64-linux-gnu/libpython3.6m.so > Many thanks, this is much appreciated! I've pasted the full Dockerfile in > https://github.com/boostorg/boost/issues/462, in case anyone is > interested. > > > > > Regards, > > Nathan > > > > On Fri, Feb 19, 2021, 4:47 AM Roy de Bokx via Boost-users < > > boost-users(a)lists.boost.org> wrote: > > > >> > >> > >> Op wo 17 feb. 2021 om 20:30 schreef Anonymous Maarten < > >> anonymous.maarten(a)gmail.com>: > >> > >>> Thanks for your answer Maarten! > >>>> Please bare with me as I'm a little new to this. Is there some way I > >>>> can change the interpreter that is used for installing boost? Or do > you > >>>> think that adapting the --prefix flag may also work? > >>>> > >>> > >>> When using the pre-built boost packages of a linux distribution > >>> (ubuntu), you're generally stuck with the versions/options that its > >>> packagers have chosen. > >>> A distribution freezes versions to make a more robust experience. > >>> > >>> Adding a `--prefix` will not help because, first of all, it's not a > >>> valid gcc option, and second, ubuntu 18.04 does not provide a > >>> libboost-python-py37 shared/static library. > >>> Do you really need python 3.7? Doesn't 3.6 suffice? > >>> > >> > >> Thanks! This helped me understanding the issue a bit further. I think > 3.6 > >> should suffice indeed, so I tried using 3.6 by removing the 3.7 > >> installation from the Dockerfile and using the -lboost_numpy3 flag > instead. > >> It seems I ran into some linking issue after this. It was able to find > >> the right numpy3.so and libboost_python3-py36.so, but I'm getting a lot > of > >> errors like these: > >> > >> //usr/lib/x86_64-linux-gnu/libboost_numpy3.so: undefined reference to > >> `PyExc_ValueError' > >> > >> //usr/lib/x86_64-linux-gnu/libboost_python3-py36.so.1.65.1: undefined > >> reference to `PyLong_AsLong' > >> > >> //usr/lib/x86_64-linux-gnu/libboost_python3-py36.so.1.65.1: undefined > >> reference to `PyNumber_InPlaceFloorDivide' > >> > >> //usr/lib/x86_64-linux-gnu/libboost_python3-py36.so.1.65.1: undefined > >> reference to `PyBool_Type' > >> etc... > >> > >> I've pasted the full docker file and logs in > >> https://github.com/boostorg/boost/issues/462 > >> Thanks again for any help. > >> > >>> > >>> If you really want to use Boost.Python + python 3.7, you can do 2 > things: > >>> - stay on ubuntu bionic and build boost yourself (or use an alternative > >>> c/c++ package manager, e.g. [conan](https://conan.io/) has a [boost > >>> package](https://conan.io/center/boost)) > >>> - more to a more recent ubuntu release. e.g. ubuntu 20.10 has python > >>> 3.8: > >>> > https://packages.ubuntu.com/groovy/amd64/libboost-python1.71-dev/filelist > >>> > >> I've also given 20.10 a try, however I ran into the same linking issues > >> as mentioned above. > >> > >>> > >>> > >>> > >>> _______________________________________________ > >> Boost-users mailing list > >> Boost-users(a)lists.boost.org > >> https://lists.boost.org/mailman/listinfo.cgi/boost-users > >> > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > https://lists.boost.org/mailman/listinfo.cgi/boost-users > > >

1 0

Re: [Boost-users] Boost cannot find numpy37 on Dockerized Ubuntu 20.04
by Roy de Bokx 22 Feb '21

22 Feb '21

Op wo 17 feb. 2021 om 20:30 schreef Anonymous Maarten < anonymous.maarten(a)gmail.com>: > Thanks for your answer Maarten! >> Please bare with me as I'm a little new to this. Is there some way I can >> change the interpreter that is used for installing boost? Or do you think >> that adapting the --prefix flag may also work? >> > > When using the pre-built boost packages of a linux distribution (ubuntu), > you're generally stuck with the versions/options that its packagers have > chosen. > A distribution freezes versions to make a more robust experience. > > Adding a `--prefix` will not help because, first of all, it's not a valid > gcc option, and second, ubuntu 18.04 does not provide a > libboost-python-py37 shared/static library. > Do you really need python 3.7? Doesn't 3.6 suffice? > Thanks! This helped me understanding the issue a bit further. I think 3.6 should suffice indeed, so I tried using 3.6 by removing the 3.7 installation from the Dockerfile and using the -lboost_numpy3 flag instead. It seems I ran into some linking issue after this. It was able to find the right numpy3.so and libboost_python3-py36.so, but I'm getting a lot of errors like these: //usr/lib/x86_64-linux-gnu/libboost_numpy3.so: undefined reference to `PyExc_ValueError' //usr/lib/x86_64-linux-gnu/libboost_python3-py36.so.1.65.1: undefined reference to `PyLong_AsLong' //usr/lib/x86_64-linux-gnu/libboost_python3-py36.so.1.65.1: undefined reference to `PyNumber_InPlaceFloorDivide' //usr/lib/x86_64-linux-gnu/libboost_python3-py36.so.1.65.1: undefined reference to `PyBool_Type' etc... I've pasted the full docker file and logs in https://github.com/boostorg/boost/issues/462 Thanks again for any help. > > If you really want to use Boost.Python + python 3.7, you can do 2 things: > - stay on ubuntu bionic and build boost yourself (or use an alternative > c/c++ package manager, e.g. [conan](https://conan.io/) has a [boost > package](https://conan.io/center/boost)) > - more to a more recent ubuntu release. e.g. ubuntu 20.10 has python 3.8: > https://packages.ubuntu.com/groovy/amd64/libboost-python1.71-dev/filelist > I've also given 20.10 a try, however I ran into the same linking issues as mentioned above. > > > >

2 2

Prooblem building software with fstream.hpp
by Mack Wallace 21 Feb '21

21 Feb '21

Hi all. I'm a noob and unfamiliar with boost. It has also been a long time since I have done any C++ programming. In any case, here are the details: I am trying to compile MecnRao/TCP-UDP-Proxy that uses the Boost Library. I am trying to compile this for Windows, ultimately Windows 10, but at the moment trying to compile on my Windows 7 VM. I am using Visual Studio Pro 2019. After trying the latest version of the Boost Library with some errors due to some deprecated members, I bounced around older versions until finding that Version 1.68.0 reduced my compile errors substantially, and of those 20 or so errors, are caused by some typedef problems in fstream.hpp. (I could be wrong, but the errors all seem to be related to fstream_fix.) Specifically, I get the following errors to begin with: 'fstream_fix<std::basic_ifstream<char,std::char_traits<char> > >' is not a variable template 'fstream_fix<std::basic_ofstream<char,std::char_traits<char> > >' is not a variable template This comes from the following lines in the fstream.hpp typedef basic_ifstream<char> ifstream; typedef basic_ofstream<char> ofstream; Where ifstream and ofstream are indicated as being redefined as #define ifstream fstream_fix<std::ifstream> #define ofstream fstream_fix<std::ofstream> Within the program with fstream_fix as template<class T> struct fstream_fix : public T { fstream_fix(){}; template<class T1> fstream_fix(T1 v1){ setlocale(LC_CTYPE, ""); T::open(v1); setlocale(LC_CTYPE, 0); } template<class T1,class T2> fstream_fix(T1 v1,T2 v2){ setlocale(LC_CTYPE, ""); T::open(v1,v2); setlocale(LC_CTYPE, 0); } template<class T1> void open(T1 v1){ setlocale(LC_CTYPE, ""); T::open(v1); setlocale(LC_CTYPE, 0); } template<class T1,class T2> void open(T1 v1,T2 v2){ setlocale(LC_CTYPE, ""); T::open(v1,v2); setlocale(LC_CTYPE, 0); } }; So I'm wondering if this is a newer/different compiler issue? Or the application itself? Or maybe just missing something like uses namespace std. I am hoping someone can help me nip this last problem so I can get this compiled. Thanks, Mack

1 0

boost::asio::read() gets stuck when there's no internet
by Child OfGod 20 Feb '21

20 Feb '21

In TgBot library i use under MSVC++, in tgbot/net/BoostHttpOnlySslClient.cpp, a call to boost::asio::read() does not return when internet is disconnected for a few minutes. I would appreciate any help to get this resolved, i.e. for the read function to return if it fails after some timeout has passed the code block in the tgbot/net/BoostHttpOnlySslClient.cpp file: [code] string BoostHttpOnlySslClient::makeRequest(const Url& url, const vector<HttpReqArg>& args) const { tcp::resolver resolver(_ioService); tcp::resolver::query query(url.host, "443"); ssl::context context(ssl::context::tlsv12_client); context.set_default_verify_paths(); ssl::stream<tcp::socket> socket(_ioService, context); connect(socket.lowest_layer(), resolver.resolve(query)); #ifdef TGBOT_DISABLE_NAGLES_ALGORITHM socket.lowest_layer().set_option(tcp::no_delay(true)); #endif //TGBOT_DISABLE_NAGLES_ALGORITHM #ifdef TGBOT_CHANGE_SOCKET_BUFFER_SIZE #if _arm64 || _WIN64 || __amd64__ || __x86_64__ || __MINGW64__ || __aarch64__ || __powerpc64__ socket.lowest_layer().set_option(socket_base::send_buffer_size(65536)); socket.lowest_layer().set_option(socket_base::receive_buffer_size(65536)); #else //for 32-bit socket.lowest_layer().set_option(socket_base::send_buffer_size(32768)); socket.lowest_layer().set_option(socket_base::receive_buffer_size(32768)); #endif //Processor architecture #endif //TGBOT_CHANGE_SOCKET_BUFFER_SIZE socket.set_verify_mode(ssl::verify_none); socket.set_verify_callback(ssl::rfc2818_verification(url.host)); socket.handshake(ssl::stream<tcp::socket>::client); string requestText = _httpParser.generateRequest(url, args, false); write(socket, buffer(requestText.c_str(), requestText.length())); string response; #ifdef TGBOT_CHANGE_READ_BUFFER_SIZE #if _M_ARM64 || _WIN64 || __amd64__ || __x86_64__ || __MINGW64__ || __aarch64__ || __powerpc64__ char buff[65536]; #else //for 32-bit char buff[32768]; #endif //Processor architecture #else char buff[1024]; #endif //TGBOT_CHANGE_READ_BUFFER_SIZE boost::system::error_code error; while (!error) { std::size_t bytes = read(socket, buffer(buff), error); response += string(buff, bytes); } return _httpParser.extractBody(response); } [/code] Thankyou in advance😀🙏

3 4

(no subject)
by Dk Jack 18 Feb '21

18 Feb '21

Hi, I am using boost 1.58 in my project. Ran into a crash in the boost filesystem library. I've included the relevant stack trace at the end of the email. My code is something like this: boost::filesystem::path fpath(mFilename.c_str()); if (!boost::filesystem::exists(fpath)) { // log a message and return. return; } auto curr_time = boost::filesystem::last_write_time(fpath); <== crash The crash is not consistent and happened randomly. I tested the above code in a small test program with just the above code. I made the input file unreadable etc, even then it was able to successfully read the last write timestamp of the file without any issues. Not sure why this particular call would throw an error. Since it's compiled with -O2, the error code is optimized out in the stack trace. Any ideas? Thanks for your help. Dk. (gdb) bt #0 0x00007f01651ba387 in raise () from /lib64/libc.so.6 #1 0x00007f01651bba78 in abort () from /lib64/libc.so.6 #2 0x00007f0160d087d5 in __gnu_cxx::__verbose_terminate_handler() () from /lib64/libstdc++.so.6 #3 0x00007f0160d06746 in ?? () from /lib64/libstdc++.so.6 #4 0x00007f0160d06773 in std::terminate() () from /lib64/libstdc++.so.6 #5 0x00007f0160d06993 in __cxa_throw () from /lib64/libstdc++.so.6 #6 0x00007f0161171f5f in boost::filesystem::detail::last_write_time(boost::filesystem::path const&, boost::system::error_code*) () from xxx.so #7 0x00007f0161089657 in last_write_time (p=...) at /usr/local/include/boost/filesystem/operations.hpp:594

2 1

Boost cannot find numpy37 on Dockerized Ubuntu 20.04
by Roy de Bokx 17 Feb '21

17 Feb '21

Hi there, I've been trying to get GP-GOMEA running in a dockerized environment <https://github.com/marcovirgolin/GP-GOMEA/issues/2>, which is a project that is built using Boost. As part of the build process, the source code is compiled by the g++ compiler, using the flag -lboost_numpy37, which fails because (it seems) numpy cannot be found. I've reported this also as an issue also in the boost repository <https://github.com/boostorg/boost/issues/462>, but mclow advised me to send this to the boost-users mailinglist too. I've create the following Dockerfile as a minimal test case, which runs into the same problem. I'm a bit of a noob when it comes to Boost and numpy, but from what I found so far on the web, this should work (but it doesn't) FROM ubuntu:20.04 ENV DEBIAN_FRONTEND noninteractive RUN apt-get update && apt-get upgrade -y && apt-get clean RUN apt-get install -y curl python3.7 python3-dev python3-distutils python3-numpy # Install latest boost version RUN apt-get -y install wget g++ RUN wget https://dl.bintray.com/boostorg/release/1.75.0/source/boost_1_75_0.tar.bz2 && \ tar --bzip2 -xf boost_1_75_0.tar.bz2 && \ cd boost_1_75_0 && \ # this will generate ./b2 ./bootstrap.sh --prefix=/usr/local && \ ./b2 --with=all install && \ sh -c 'echo "/usr/local/lib" >> /etc/ld.so.conf.d/local.conf' && \ ldconfig # Check numpy installation RUN find / -name "numpy.hpp" RUN find / -name "libboost_numpy37.so" RUN find / -name "libboost_numpy3.so" RUN find / -name "libboost_numpy.so" RUN ld -lboost_numpy37 --verbose This eventually results in the following error: The command '/bin/sh -c ld -lboost_numpy37 --verbose' returned a non-zero code: 1, because it could not find any libboost_numpy37.so or libboost_numpy37.o file. The full logs are attached in the GH issue linked above. Did anyone encounter something similar, or does anyone have an idea what could cause this? Any help is much appreciated! -Roy

2 2

How to change read/write method of source/sink device in C++ boost::iostreams?
by mostaan fereidooni 16 Feb '21

16 Feb '21

I'm trying to get familiar with boost::iostream, so in a example program I'm writing, I want to read a text from a file and write it to file. I would use my inherited class from file_source/file_sink as device to read/write. In the read method, my class needs to add each character with one and write method needs to subtract one from each character. First of all, I want to make sure that the reading part of the program works properly so you can see the code as follow: #include <boost/iostreams/stream.hpp>#include <fstream>#include "MyFileSource.h"#include <iostream>using namespace std;using namespace boost::iostreams;int main(){ MyFileSource<char> fileSource("source.txt"); stream<MyFileSource<char>> myStream(fileSource); std::cout << myStream.rdbuf(); fileSource.close(); } and my inherited source device code is as follow: template <typename charType>class MyFileSource : public boost::iostreams::file_source {public: MyFileSource(const std::string& path) : boost::iostreams::file_source(path) { file_path = path; if (!is_open()) open(path); seek(0, ios::end); sizeOfFile = seek(0, ios::cur); seek(0, ios::beg); buffer = new charType[sizeOfFile]; } std::streamsize read(charType*, std::streamsize) { std::streamsize readCount = boost::iostreams::file_source::read(buffer, sizeOfFile); if (readCount > 0) { std::string result(buffer, readCount); for (char& c : result) c++; finalResult = result; } return readCount; } private: string file_path; int sizeOfFile; charType* buffer; std::string finalResult; }; unfortunately, the result of *std::cout << myStream.rdbuf()* with above read method is nothing while if I delete the read method of MyFileSource class to use the read method of parent, the result will be correct. Any help will be appreciated.

1 0

How to link boost library DLLs?
by Anand Arumugam 14 Feb '21

14 Feb '21

Hello all, How to properly link boost library DLLs? I have #define-d the following: #define BOOST_ALL_DYN_LINK #define BOOST_DYN_LINK #define BOOST_THREAD_USE_DLL #define BOOST_THREAD_PROVIDES_FUTURE_CONTINUATION #define BOOST_THREAD_VERSION 4 And I still get the following problem: --------------------------- testprogs.exe - System Error --------------------------- The code execution cannot proceed because boost_thread-vc142-mt-gd-x64-1_75.dll was not found. Reinstalling the program may fix this problem. --------------------------- OK --------------------------- I get the same error when I try to run the program using DLLs that I built and while running using the prebuilt binaries. Not sure what step I'm missing. The program runs fine if I build using static libs. The problem is only with DLLs. Any help is much appreciated. Thanks, Anand.

3 3

Boost.Asio as "thread-pool": How to apply back-pressure?
by Dominique Devienne 10 Feb '21

10 Feb '21

Hi, I'm using Boost.ASIO, not for networking, but simply to parallelize work items, with a simple graph of "processing nodes" as detailed below. It's working fine, but uses too much memory. I'd like insights on limiting memory use via "throttling", or what I've also seen called "back-pressure". At a high level, I process two files (A and B) composed of several "entries" each, extracting a subset or a transformation of those entries, that I then write into an output file (C). (those 3 files reach into the many GBs, thus the need for parallelism, and limiting memory use). Extracting entries from A and B are independent operations, implemented single-threaded, producing independent work items (for subsetting or transforming each item), A#1...A#n, and B#1..B#m. That's the "fan-out" part, with each work-item (task) scheduled on any thread of the ASIO pool, since independent. Writing to C is also single-threaded, and needs to "fan-in" the work posted by the A#n and B#m functors, and I serialize that via posting to a C-specific strand (still on any thread, as long as serialized, doesn't matter). Lets call all those tasks writing to C the C#n+m tasks, which are posted to the strand via the A#s and B#s. My issue is that Boost.Asio seems to schedule an awful lots of A# and B# tasks, before getting to the C# tasks, which results in accumulating in memory too many C# tasks, and thus using too much memory. I don't see a way to force more C "downstream" tasks to be scheduled, before processing so much A and B tasks, and accumulating pending C tasks in the work queue, thus using too much memory again. Could someone please recommend a way to have a more balanced flow of tasks in the graph? Or alternative designs even, if what I do above is not ideal. Is Boost.Asio even suitable in this case? Thanks, --DD

7 17

[boost-process] why does my child process not get EOF on stdin
by harald 01 Feb '21

01 Feb '21

Dear community, dear experts! I am trying to use boost::process to call weasyprint to convert HTML to a picture. To do that I wrote a test program (further down in the mail). This worked fine and did what i expected. But it stopped working as soon as I tried to convert two files at the same time by changing new renderer_t(io_context, "<head></head><body></body>"); in main to new renderer_t(io_context, "<head></head><body></body>"); new renderer_t(io_context, "<head></head><body></body>"); Now weasyprint hangs. I changed the call to weasyprint to weasyprint2, which is a short bash script for testing purposes: --------------------------------------------------------------------------------- #! /bin/bash cat > /dev/null echo "This should be a PNG picture" --------------------------------------------------------------------------------- It reads stdin until it gets EOF and then writes something to stdout before terminating. Same result. It seems that my program does not close stdin of the child, so it never gets EOF on stdin. But only when more than one child process is running at the same time. So obviously I am doing something wrong, but I have no idea what! Does anybody have a hint for me? I am on xubuntu 20.10 compiler is g++ (Ubuntu 10.2.0-13ubuntu1) 10.2.0, boost version 1.75.0 compiler command line (from my IDE): g++ -c main.cpp -g -O0 -Wall -Wextra -std=c++17 -o build-Debug/main.cpp.o -I. -I. --------------------------------------------------------------------------------- #include <boost/smart_ptr/intrusive_ptr.hpp> #include <boost/smart_ptr/intrusive_ref_counter.hpp> #include <boost/process.hpp> #include <boost/asio/write.hpp> #include <iostream> namespace bp = boost::process; bool is_eof( std::error_code error) { boost::system::error_code eof = boost::asio::error::eof; return error == eof; } struct renderer_t : public boost::intrusive_ref_counter<renderer_t> { using pointer = boost::intrusive_ptr<renderer_t>; boost::asio::io_context &io_context; const std::string html; bp::child child; bp::async_pipe in; bp::async_pipe out; bp::async_pipe err; std::array<unsigned char, 256> outbuf; std::array<char, 256> errbuf; std::vector<unsigned char> result; std::error_code result_error; std::string errmsg; ~renderer_t() { std::cout << "renderer_t::~renderer_t\n"; if (!errmsg.empty()) std::cerr << "renderer_t::~renderer_t: stderr: " << errmsg << "\n"; } renderer_t( boost::asio::io_context &io_context, const std::string &html) : io_context(io_context), html(html), in(io_context), out(io_context), err(io_context) { post( io_context, [self = pointer(this)]() { self->start(); }); } void start() { std::error_code ec; std::cout << "renderer_t::start\n"; bp::child c( "weasyprint2 -m screen -p -f png - /dev/stdout", bp::std_in < in, bp::std_out > out, bp::std_err > err, bp::on_exit=[self = pointer(this)]( int exit, std::error_code error) { self->on_exit(error, exit); }, bp::start_dir="/data/build/", io_context, ec); if (ec) { std::cerr << "renderer_t::start: creating child failed: " << ec.message() << "\n"; if (!result_error) result_error = ec; return; } child = std::move(c); boost::asio::async_write( in, boost::asio::buffer(html), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_write(error, bytes); }); out.async_read_some( boost::asio::buffer(outbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_out(error, bytes); }); err.async_read_some( boost::asio::buffer(errbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_err(error, bytes); }); } void on_write( std::error_code error, std::size_t bytes) { std::cout << "renderer_t::on_write\n"; if (error) { std::cerr << "renderer_t::on_write: failed: " << error.message() << "\n"; if (!result_error) result_error = error; return; } if (bytes != html.size()) { std::cerr << "renderer_t::on_write: short write\n"; } boost::system::error_code ec; in.close(ec); if (ec) { std::cerr << "renderer_t::on_write: close failed: " << error.message() << "\n"; } } void on_read_out( std::error_code error, std::size_t bytes) { std::cout << "renderer_t::on_read_out\n"; if (is_eof(error)) { std::cout << "renderer_t::on_read_out: EOF\n"; return; } else if (error) { std::cerr << "renderer_t::on_read_out: failed: " << error.message() << "\n"; if (!result_error) result_error = error; return; } else { result.insert( end(result), begin(outbuf), begin(outbuf) + bytes); out.async_read_some( boost::asio::buffer(outbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_out(error, bytes); }); } } void on_read_err( std::error_code error, std::size_t bytes) { std::cout << "renderer_t::on_read_err\n"; if (is_eof(error)) { std::cout << "renderer_t::on_read_err: EOF\n"; return; } else if (error) { std::cerr << "renderer_t::on_read_err: failed: " << error.message() << "\n"; if (!result_error) result_error = error; return; } else { std::string e(begin(errbuf), begin(errbuf) + bytes); std::cerr << "renderer_t::on_read_err: from stderr: " << e << "\n"; errmsg.insert( end(errmsg), begin(errbuf), begin(errbuf) + bytes); err.async_read_some( boost::asio::buffer(errbuf), [self = pointer(this)]( std::error_code error, std::size_t bytes) { self->on_read_err(error, bytes); }); } } void on_exit( std::error_code error, int exit) { std::cout << "renderer_t::on_exit\n"; if (error) { std::cerr << "renderer_t::on_exit: error: " << error.message() << "\n"; if (!result_error) result_error = error; return; } if (exit) { std::cerr << "renderer_t::on_exit: weasyprint returned " << exit << "\n"; if (!result_error) result_error = make_error_code(std::errc::no_such_process); } } }; int main() { boost::asio::io_context io_context; bp::async_pipe in(io_context); new renderer_t(io_context, "<head></head><body></body>"); io_context.run(); return 0; } --------------------------------------------------------------------------------- Regards Harald

1 0