- Boost-users - lists.boost.org

Re: [Boost-users] [Boost.Asio] tutorial #1 code does not compile (g++)
by Andrew McFarlane 31 Jan '20

31 Jan '20

Okay, so I have made a bit of progress. After building Boost.Asio with: b2 --with-system --with-thread --with-date_time --with-regex --with-serialization stage , and building Boost.Chrono with (replacing bjam with b2): bjam libs/chrono/build The code is now compiling with the following g++ command: g++ -v -Wall -L ${BOOST_ROOT}/stage/lib -L ${BOOST_ROOT}/bin.v2/libs/chrono/build/clang-darwin-11.0/debug/threading-multi/visibility-hidden -lboost_chrono -lboost_date_time -lboost_system -I. -I${BOOST_ROOT} -o main main.cpp However, when I go to run main, the program crashes with the following message: dyld: Library not loaded: @rpath/libboost_chrono.dylib Referenced from: /Users/ajm/Projects/boost-threads/ex1/./main Reason: image not found Abort trap: 6 I suspect that there is something wrong with the Boost.Chrono dynamic library file that was built (probably because of how I built it), but I am not sure what it would be. Any suggestions? Thanks, *Andrew J. E. McFarlane*

3 2

Re: [Boost-users] [Boost.Asio] tutorial #1 code does not compile (g++)
by Andrew McFarlane 29 Jan '20

29 Jan '20

Hi Richard, I suspect you and David are both correct; I need to link boost_chrono. I found here https://www.boost.org/doc/libs/1_72_0/doc/html/chrono/users_guide.html "If BOOST_CHRONO_HEADER_ONLY <https://www.boost.org/doc/libs/1_72_0/doc/html/chrono/reference.html#chrono…> is not defined you need to compile it and build the library before use". This aligns with what you are saying. However, the command it mentions to use, >> bjam libs/chrono/build does not work, even when I am in the boost directory (bjam is not defined). In addition, adding -lboost_chrono or -L{BOOST_ROOT} does not help my case. After reading this article about static and dynamic linked libraries https://medium.com/@dkwok94/the-linking-process-exposed-static-vs-dynamic-l… I suspect I must append the path of boost_chrono to my LD_LIBRARY_PATH variable. Am I correct in this thinking? If so, where the heck is boost_chrono located? I could not find a .a or .so file in libs/chrono/ anywhere. Do I need to build the static/dynamic library myself? Please advise. I apologize for the elementary questions; my compiler and Unix knowledge could be way better, which is something I am working on. Thanks *Andrew J. E. McFarlane* *Cell: (236) 888-1376* On Tue, Jan 28, 2020 at 11:33 PM <boost-users-request(a)lists.boost.org> wrote: > 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. [Boost.Asio] tutorial #1 code does not compile (g++) > (Andrew McFarlane) > 2. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Vinnie Falco) > 3. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Andrew McFarlane) > 4. Re: [Boost.Asio] tutorial #1 code does not compile (g++) > (Richard Hodges) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 Jan 2020 17:14:58 -0800 > From: Andrew McFarlane <andrew.mcfarlane52(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [Boost.Asio] tutorial #1 code does not compile > (g++) > Message-ID: > <CAG90r9SPGR= > wRUykmftmxTM6oUKbTZYoyat_BR9ufaNpQ0g4Rw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi All, > > I am attempting to get acquainted with C++ multithreaded network > programming. I have a background in such topics within Java but considering > how different C++ is, I am starting from ground zero. > > I have copied the code from tutorial #1 into my IDE, Timer.1: Using a timer > synchronously: > > https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/tutorial/tuttimer… > (follow > the link for code). > > When I tried to compile this (using g++) with the following command: > > g++ -v -I${BOOST_ROOT} -I. -o main main.cpp > (BOOST_ROOT is where I have boost installed), I get the following output: > > Undefined symbols for architecture x86_64: > > "boost::chrono::steady_clock::now()", referenced from: > > boost::asio::detail::chrono_time_traits<boost::chrono::steady_clock, > boost::asio::wait_traits<boost::chrono::steady_clock> >::now() in > main-c86634.o > > ld: symbol(s) not found for architecture x86_64 > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > Note this is the non-verbose output (I would rather not post the verbose > output, as I am trying to keep this post short). > > I did some digging of my own on Boost's steady_timer documentation and > tried to follow that style, as you can find here: > > https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/reference/steady_… > In other words, I replace the two-parameter boost::asio::steady_timer ctor > call with a single-parameter ctor call in which I pass an io_context, > followed by > t.expires_after(std::chrono::seconds(5)); > > This generated another compiler error, this one to do with 'no viable > conversion'. See here: > > main.cpp:10:21: error: no viable conversion from 'std::chrono::seconds' > (aka > > 'duration<long long>') to 'const > > boost::asio::basic_waitable_timer<boost::chrono::steady_clock, > > boost::asio::wait_traits<boost::chrono::steady_clock>, > > boost::asio::executor>::duration' (aka 'const duration<long long, > > ratio<(1L), (1000000000L)> >') > > t.expires_after(std::chrono::seconds(5)); > Again, there is more output that I have omitted for brevity. If anyone > would like to see the rest of the output, I will gladly supply it. > > The bottom line is I am not sure what the problem is, or why I am having to > debug tutorial code in the first place. This should be relatively simple to > "plug & play", should it not? Does this have to do with my compiler? BTW, I > am running Mac OS X. > > Thanks in advance for the help. > > Sincerely, > > *AJ* >

2 1

[Boost.Asio] tutorial #1 code does not compile (g++)
by Andrew McFarlane 29 Jan '20

29 Jan '20

Hi All, I am attempting to get acquainted with C++ multithreaded network programming. I have a background in such topics within Java but considering how different C++ is, I am starting from ground zero. I have copied the code from tutorial #1 into my IDE, Timer.1: Using a timer synchronously: https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/tutorial/tuttimer… (follow the link for code). When I tried to compile this (using g++) with the following command: g++ -v -I${BOOST_ROOT} -I. -o main main.cpp (BOOST_ROOT is where I have boost installed), I get the following output: Undefined symbols for architecture x86_64: "boost::chrono::steady_clock::now()", referenced from: boost::asio::detail::chrono_time_traits<boost::chrono::steady_clock, boost::asio::wait_traits<boost::chrono::steady_clock> >::now() in main-c86634.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Note this is the non-verbose output (I would rather not post the verbose output, as I am trying to keep this post short). I did some digging of my own on Boost's steady_timer documentation and tried to follow that style, as you can find here: https://www.boost.org/doc/libs/1_72_0/doc/html/boost_asio/reference/steady_… In other words, I replace the two-parameter boost::asio::steady_timer ctor call with a single-parameter ctor call in which I pass an io_context, followed by t.expires_after(std::chrono::seconds(5)); This generated another compiler error, this one to do with 'no viable conversion'. See here: main.cpp:10:21: error: no viable conversion from 'std::chrono::seconds' (aka 'duration<long long>') to 'const boost::asio::basic_waitable_timer<boost::chrono::steady_clock, boost::asio::wait_traits<boost::chrono::steady_clock>, boost::asio::executor>::duration' (aka 'const duration<long long, ratio<(1L), (1000000000L)> >') t.expires_after(std::chrono::seconds(5)); Again, there is more output that I have omitted for brevity. If anyone would like to see the rest of the output, I will gladly supply it. The bottom line is I am not sure what the problem is, or why I am having to debug tutorial code in the first place. This should be relatively simple to "plug & play", should it not? Does this have to do with my compiler? BTW, I am running Mac OS X. Thanks in advance for the help. Sincerely, *AJ*

4 4

[Regex]: Can a possible non-matched group be prevented from being reported?
by Eko palypse 24 Jan '20

24 Jan '20

Hopefully I'm not posting this again. Hello, I'm wrapping boost::regex with cython to be able to call it from python. Assuming a "Hello World" text and a regex (\w+)*. This results in two matches. groups ('Hello', 'Hello') lastindex 1 group:0 Hello start 0 end 5 group:1 Hello start 0 end 5 groups ('', '') lastindex 1 group:0 start 5 end 5 group:1 start -1 end -1 I understand, that there is always the main match in group0 and matches from capturing groups in group1 ... As we see, the second match, the zero-length-width match, reports two groups but the second group returns -1. Is it possible to prevent such matches to be reported beforehand? Or is it needed to iterate over the groups to eliminate those? Just in case it is needed to see my code logic, this is what I'm doing currently def unicode_research_iter(const wchar_t* text, wchar_t* pattern, int flags): cdef: wcmatch what size_t _length size_t _position wcregex_iterator start, end try: start = make_regex_iterator(text, <wregex>pattern, match_flags.match_perl) end = wcregex_iterator() while (start != end): what = <wcmatch>deref(start) if not what.empty(): match_object = UnicodeMatch.from_instance(what) yield match_object else: print('Empty match result: ??') inc(start) # increment except Exception as e: raise RuntimeError(f'{e}') Thank you Eren

1 0

Fwd: [GSoC 2020][GIL] Mentors and project proposals
by Mateusz Loskot 17 Jan '20

17 Jan '20

FYI, https://lists.boost.org/boost-gil/2020/01/0372.php, copied below. ---------- Forwarded message --------- From: Mateusz Loskot <mateusz(a)loskot.net> Date: Fri, 17 Jan 2020 at 23:17 Subject: [GSoC 2020] Mentors and project proposals To: <boost-gil(a)lists.boost.org> Dear All, I have started collecting proposals of GIL projects for GSoC 2020. On the Boost official GSoC 2020 wiki, I've added Image Processing project as continuation of Miral's project from 2019: https://github.com/boostorg/boost/wiki/Google-Summer-of-Code:-2020 If Boost will participate, I should be able to mentor this year. Stefan, are you on board too? Who else? If there are students and mentors interested in GIL, it is time to stop being shy ;) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[Graph] Large incoming changes to Boost.Graph master.
by John Maddock 08 Jan '20

08 Jan '20

Dear all, Boost.Graph has had no maintainer for some time, but the CMT has been busy fixing bugs none the less. Unfortunately, other than some trivial fixes to docs and some directory refactoring, nothing much has been merged to master in a good while . On the plus side, develop is now in a better tested tested state than IMO it has ever been, however the change set is rather large so the potential to mess up somebodies code is certainly there: https://github.com/boostorg/graph/pull/196. So... this is both a heads up, and a plea: if you have any mission critical code using the Graph library, could you please test against current develop and report any problems? If you don't want to mess about with git, download from https://github.com/boostorg/graph/archive/develop.zip and place zipfile-contents/libs/graph/include in your include path ahead of that for Boost-1.72. Many thanks, John.

1 0

Re: [Boost-users] [boost] Retirement as Review Wizard
by Matt Calabrese 07 Jan '20

07 Jan '20

On Sat, Jan 4, 2020, 20:23 Ronald Garcia via Boost <boost(a)lists.boost.org> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > Thanks for everything, Ron! >

1 0

Re: [Boost-users] [boost-steering] Retirement as Review Wizard
by Antony Polukhin 06 Jan '20

06 Jan '20

Many thanks for all your contributions! On Sat, Jan 4, 2020, 22:03 Ronald Garcia <rxg(a)cs.ubc.ca> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > > > Sincerely, > Ron Garcia > Boost Co-Review Wizard > > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google Groups > "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to boost-steering+unsubscribe(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/BFFCD488-2E57-4161-8D13-2D… > . >

1 0

Re: [Boost-users] [boost-steering] Retirement as Review Wizard
by Jon Kalb 06 Jan '20

06 Jan '20

Ron, For myself and on behalf of the Boost Steering Committee, thanks very much for both your effort on behalf of the Boost community and the leadership that you've demonstrated. Jon On Sat, Jan 4, 2020 at 2:03 PM Ronald Garcia <rxg(a)cs.ubc.ca> wrote: > Dear Boosters and Boost Steering Committee, > > After roughly 14 years as a Boost Co-Review Wizard, I feel that the time > has come for me to step down from the position, and make room for a new > face with fresh ideas. It has been my pleasure to serve in this position > for this time alongside first Tom Brinkman and now John Phillips. > I look forward to seeing what the next 14+ years of Boost brings! > > > Sincerely, > Ron Garcia > Boost Co-Review Wizard > > > > > -- > The Boost Steering Committee webpage: > https://sites.google.com/a/boost.org/steering/ > --- > You received this message because you are subscribed to the Google Groups > "Boost Steering Committee" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to boost-steering+unsubscribe(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/boost-steering/BFFCD488-2E57-4161-8D13-2D… > . >

1 0

[Geometry] Trouble with adapting geometric objects to Eigen to use convex_hull on multiple polygons
by Rostyslav-Paul Wilhelm 06 Jan '20

06 Jan '20

1 0