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

boost.msm and boost.mp11
by Bogdan 19 Dec '17

19 Dec '17

Now that boost 1.66 includes mp11, is there a plan to upgrade the meta-state machine library (boost.msm) to something less macro dependent? Thank you, Bogdan

1 0

Adding C++/CLI code to my project makes app crash on startup
by Sergio Basurco 19 Dec '17

19 Dec '17

Hi, I'm using Boost 1.65.1 with Visual Studio 2015 (v140 compiler). Also, I'm using the following libs dynamically: boost_unit_test_framework boost_log boost_filesystem boost_thread boost_system boost_log_setup boost_chrono boost_date_time boost_regex And I want to add C++/CLI code which is built with /clr. This used to work with v110 and Boost 1.57. Now I'm getting this error just when launching the application. *0xc000007b* All binaries are 32bits. I'm also using the following define: BOOST_ALL_DYN_LINK Any idea on why this may happen? -- Saludos / Best regards, *Sergio Basurco* Coherent Synchro

7 12

Issue installing boost 1.65.1 on Centos 7
by Forum (io) 15 Dec '17

15 Dec '17

Dear All, I actually have a problem installing OpenEXR on a Centos 7. My problem is around ilmbase package and pyilmbas *and boost* as boost is required. And I have issue installing boost that I download from here https://gist.github.com/1duo/2d1d851f76f8297be264b52c1f31a2ab Before i decrive my problem let me explain where I looking around boost. When I compil ilambase, I got this error message: /$ ./compile --prefix=/opt/ilmbase2-2-0/ Both display this message/ / /checking for boost::python... no *** Could not run the boost::python test program, checking why... *** The test program could not be compiled. Is boost::python installed? *** Check that the cflags (below) includes the boost::python include directory *** *** Flags used by the test: *** cflags: -g -O2 -I/usr/include/python2.7 -g -O2 -I/usr/include/python2.7 *** ldflags: -L/opt/ilmbase-2-2-0/lib -L/usr/lib64 -L/opt/ilmbase-2-2-0/lib -L/usr/lib64 *** *** You can also run configure with --disable-boostpythontest to skip this test. configure: error: Could not compile boost::python test program. /Someone suggested me to install boost as a share. I downloaded the boost 1.65.1 an untar it into /root/install-package/ Then I tried the following command: cd /root/install-package/boost_1_65_1 sudo ./bootstrap.sh --prefix=/opt/boost_1.65.1 sudo ./b2 address-model=64 variant=release threading=multi link=shared Note that my first attend was with that command cd /root/install-package/boost_1_65_1 sudo ./bootstrap.sh --prefix=/opt/boost_1.65.1 sudo ./b2 And boost was install in /opt/boost_1.65.1 But since I use the command sudo ./b2 address-model=64 variant=release threading=multi link=shared No folder was created in /opt/boost_1.65.1 and at the of the process, this was displayed The following directory should be added to compiler include paths: /root/install-package/boost_1_65_1 The following directory should be added to linker library paths: /root/install-package/boost_1_65_1/stage/lib Then it's look like it boost has been installed in the same folder, where it has been extracted *The my question, what did I do wrong and how can I install boost in /opt/boost_1.65.1 and make it share for ilmbase and OpenEXR? * Feel you free to ask addintionnal question if I missed to provide you Many thank for your help Cheers Pierre* *

2 1

Named pipe available to other processes (boost::process)
by Mike Gibson 15 Dec '17

15 Dec '17

It seems that boost::process::basic_pipe::basic_pipe(const std::string& name) on posix creates a fifo using mkfifo, opens it and then unlinks it. I imagine there's a good reason for the unlink step in some situations, but it's causing me issues. I would like to use the fifo later with a non-boost::process started process, so by the time I get around to starting the second process, it can't access the fifo. Is there any workaround for this?

1 0

Re: [Boost-users] [boost] [release] Boost 1.66.0 Release Candidate 2
by Marcel Raad 15 Dec '17

15 Dec '17

> -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Olaf van > der Spek via Boost > Sent: Donnerstag, 14. Dezember 2017 16:11 > To: boost(a)lists.boost.org > Cc: Olaf van der Spek <ml(a)vdspek.org>; boost-users(a)lists.boost.org > Subject: Re: [boost] [release] Boost 1.66.0 Release Candidate 2 > > On Thu, Dec 14, 2017 at 2:03 PM, Daniel James via Boost > <boost(a)lists.boost.org> wrote: > > As always, the release managers would appreciate it if you download > > the candidate of your choice and give building it a try. Please report > > both success and failure, and anything else that is noteworthy. > > "Info: Boost.Config is older than your compiler version - probably > nothing bad will happen - but you may wish to look for an update Boost > version. Define BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE to > suppress > this message." > generates so much noise, could it be suppressed for 15.5 if the > updates to config can't be included? The message itself tells a trivial way to suppress it - so I don't see any problem? Marcel

1 0

Re: [Boost-users] [boost] [release] Boost 1.66.0 Release Candidate 2
by Marcel Raad 15 Dec '17

15 Dec '17

Hi, > -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Olaf van > der Spek via Boost > Sent: Donnerstag, 14. Dezember 2017 16:02 > To: boost(a)lists.boost.org > Cc: Olaf van der Spek <ml(a)vdspek.org>; boost-users(a)lists.boost.org > Subject: Re: [boost] [release] Boost 1.66.0 Release Candidate 2 > > On Thu, Dec 14, 2017 at 2:03 PM, Daniel James via Boost > <boost(a)lists.boost.org> wrote: > > The second release candidates for the 1.66.0 release are now available at: > > > > <https://dl.bintray.com/boostorg/prerelease/> > > Repository path missing or not specified. the correct path seems to be https://dl.bintray.com/boostorg/release/1.66.0/source/ Marcel

3 2

ASIO and windows registered IO
by Tore Halvorsen 15 Dec '17

15 Dec '17

Hi, Have anyone tried to use the windows registered IO functionality with ASIO?

2 1

[release] Boost 1.66.0 Release Candidate 2
by Daniel James 14 Dec '17

14 Dec '17

The second release candidates for the 1.66.0 release are now available at: <https://dl.bintray.com/boostorg/prerelease/> The in progress release notes are: <http://www.boost.org/users/history/in_progress.html> Library documentation is available at: <http://www.boost.org/doc/libs/1_66_0/> The SHA256 checksums are as follows: 596389389c005814ecb2a6b64c31dccd2c3e6fbc5a802b4dfada999ae5844628 boost_1_66_0_rc2.7z 5721818253e6a0989583192f96782c4a98eb6204965316df9f5ad75819225ca9 boost_1_66_0_rc2.tar.bz2 bd0df411efd9a585e5a2212275f8762079fed8842264954675a4fddc46cfcf60 boost_1_66_0_rc2.tar.gz e1c55ebb00886c1a96528e4024be98a38b815115f62ecfe878fcf587ba715aad boost_1_66_0_rc2.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.

2 1

Re: [Boost-users] [boost] [release] Boost 1.66.0 Release Candidate 2
by Daniel James 14 Dec '17

14 Dec '17

On 14 December 2017 at 15:02, Olaf van der Spek <ml(a)vdspek.org> wrote: > On Thu, Dec 14, 2017 at 2:03 PM, Daniel James via Boost > <boost(a)lists.boost.org> wrote: >> The second release candidates for the 1.66.0 release are now available at: >> >> <https://dl.bintray.com/boostorg/prerelease/> > > Repository path missing or not specified. Sorry, should be: https://dl.bintray.com/boostorg/release/1.66.0/source/

1 0

Newbie: BGL & planar graphs
by ano kato 13 Dec '17

13 Dec '17

Hello everyone! I am using BGL to test for the planarity of drawings of graphs. The coordinates are hardcoded into the source code. Here's what the graph should look like: <https://i.imgur.com/UGA0mRB.png>. This definitely isn't planar and yet is_straight_line_drawing() returns 1! I'm quite confused. Am I doing something wrong? Thank you to anyone who replies. #include <iostream> #include <vector> #include <boost/graph/adjacency_list.hpp> #include <boost/property_map/property_map.hpp> #include <boost/graph/is_straight_line_drawing.hpp> using namespace boost; typedef struct { size_t x,y; } coord_t; int main(void) { typedef adjacency_list<vecS, vecS, undirectedS, property<vertex_index_t, int> > graph; graph Moser(7); add_edge(0,1,Moser); add_edge(0,6,Moser); add_edge(0,4,Moser); add_edge(1,6,Moser); add_edge(1,2,Moser); add_edge(2,6,Moser); add_edge(2,5,Moser); add_edge(2,3,Moser); add_edge(3,4,Moser); add_edge(4,5,Moser); graph G(Moser); int k = num_vertices(G); typedef std::vector<coord_t> cvec; typedef boost::iterator_property_map <cvec::iterator, property_map<graph, vertex_index_t>::type // ? > foo_t; cvec v(num_vertices(G)); foo_t drawing(v.begin(), get(vertex_index, G)); coord_t x[k]; x[0].x = 20; x[0].y = 10; x[1].x = 50; x[1].y = 10; x[2].x = 58; x[2].y = 52; x[3].x = 00; x[3].y = 30; x[4].x = 35; x[4].y = 50; x[5].x = 12; x[5].y = 51; x[6].x = 70; x[6].y = 30; graph_traits<graph>::vertex_iterator vi, vi_end; for(boost::tie(vi, vi_end) = vertices(G); vi != vi_end; ++vi) put(drawing, *vi, x[*vi]); if(is_straight_line_drawing(G,drawing)) std::cout << "This is a straight line planar drawing!" << std::endl; return 0; }

2 2