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

Boost library name formats
by Damien 15 Mar '19

15 Mar '19

Hello, For several years now we've built Boost libraries on Windows with a minimal set of tags in the library and dll names. Our dlls and libs have looked like this: boost_atomic-mt-gd.dll boost_atomic-mt-gd.lib etc. We just upgraded from 1.65.1 to 1.69 and the same bjam command (with a new bootstrapped bjam) is now giving us an extra x64 tag: boost_atomic-mt-gd-x64.dll boost_atomic-mt-gd-x64.lib This is on VS2017 15.9.9. The bjam command we've used for years is: bjam.exe --toolset=msvc address-model=64 --stagedir=./stage64debug --build-dir=./build64debug --layout=tagged --without-mpi variant=debug link=shared threading=multi runtime-link=shared install --prefix=./win64debug/indep --exec-prefix=./win64debug/bin --libdir=./win64debug/lib --includedir=./win64debug/include Has a default setting in bjam been changed? What can we add to the bjam command to get back to the old minimal names? Thanks in advance. Damien

2 2

Help Needed with C++ SSL-using code
by Osman Zakir 15 Mar '19

15 Mar '19

I followed the Boost.Beast examples for the SSL, sync server and client code and loaded root certificates from the Windows root cert store (or at least tried to), but now I can't even get to my app in my browser anymore for some reason. Here's the link to the GitHub repository with all of the source code: https://github.com/DragonOsman/currency_converter . Any help would be appreciated. [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/DragonOsman/currency_converter> GitHub - DragonOsman/currency_converter: Application for Computer Science course<https://github.com/DragonOsman/currency_converter> Google Maps + Currency Converter Web Application. Application for Computer Science course. This is a currency converter web application with the frontend and a backend. github.com

1 0

Re: [Boost-users] [boost] Networking TS + Beast, NEW Tutorials, Read this to learn std::net !!!
by Vinnie Falco 15 Mar '19

15 Mar '19

On Thu, Mar 14, 2019 at 5:09 PM Ivan Matek <libbooze(a)gmail.com> wrote: > Quite a weird pattern, where buffer does not have member begin, end. > Maybe a sentence or two describing the rationale and complexity would be nice. > I know it is O(1), but it is weird that begin/end are called on pointer. Yeah, well... that's a sore subject. First of all I did not invent these buffer concepts, they are part of Asio and Networking TS. And they *used* to have begin() and end(), but then the C++ Standards Committee decided that they didn't like `const_buffers_1` and `mutable_buffers_1`, so they got rid of them in the TS draft. Then they realized that having `const_buffer::begin()` would be confusing. Does it refer to the beginning of the buffer sequence, or does it refer to the first byte of that buffer? They decided to get rid of begin/end entirely for the buffer types and add buffer_sequence_begin and buffer_sequence_end in its place. And this is why we can't have nice things. > > std::size_t read_line > I am tired, but is this function O(n^2)? It starts over from the beginning of the range so there can be some overlap of the searching, yes. > cb += bytes_transferred; // adjust the pointer and size > I would maybe switch to write instead of write_some to keep the code shorter, and mention write_some as another option in text. Well the purpose of this example is to show the looping. > [](error_code ec, std::size_t bytes_transferred) > For learning purposes I would capture something in lambda by value and note that reference capture would be buggy. That is something I might consider!! Remember though I"m stuck in C++11 so no lambda capture assignment expressions. Appreciate the feedback! Regards

2 1

Coordinating Boost Releases with compiler releases
by Marshall Clow 14 Mar '19

14 Mar '19

In the thread "MSVC 2019 and 1.70 beta", there has been a discussion about what to do about support for MSVC 2019, which is due to be released right about the same time that Boost 1.70. One person suggested that we delay the boost release until after the MSVC release (I think the suggestion was "May"). This general question has been discussed before (several times), since tools get released fairly often - and so does Boost. In general, I am not in favor of delaying boost releases in order to add support for 'about to be released' development tools. There are two main reasons for this: * There's always another compiler / tool about to be released. Clang 8 is imminent - currently at RC5. GCC 9.1 is scheduled to be released in early May. * Boost releases happen every four months. August is not really that far off. People who want support for tool XXXX can use "the trunk", getting it either from git or from bintray. [ Everyone knows about the tarballs at bintray, right? https://dl.bintray.com/boostorg/master/ ] Also, if we were to delay the boost release until May, then what would happen to the August release? The release process for 1.71.0 is scheduled to start at the end of June. -- Marshall

3 3

(no subject)
by Marshall Clow 13 Mar '19

13 Mar '19

Boost release 1.70.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.70.0.beta1/source/> The SHA256 checksums are as follows: dbf89645e509acb2e53eac3c633834f1dec80bd8622e6e652a9741dcf0807f17 ./boost_1_70_0_b1.7z 957b984b58656a3ec00661ecad7ef82e3a094bad36e37b9e6624843237854679 ./boost_1_70_0_b1.tar.bz2 76d149c1fb9e8a5ceb3bc1e5587edc40fa79a43e8b990d877c2210f0382b9421 ./boost_1_70_0_b1.tar.gz 71e990b2c26880521fd98459b184ee172ce1c46dcf554b6eaab7776b8b6369a6 ./boost_1_70_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_70_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

2 1

Issue with boost::geometry::intersection
by Heriberto Delgado 13 Mar '19

13 Mar '19

I'm having an issue while using boost::geometry to find the intersection of two specific polygons, and looking at the evidence in front of me I can't help but think this might be a bug in the library. The two polygons in question are: POLYGON((16.8739 0.353458,8.80872e-14 5.50545e-15,0.266003 -12.6988,17.1399 -12.3454,16.8739 0.353458)) POLYGON((-4.53257e-19 2.16383e-17,9.99781 0.209424,10.1459 -6.86009,0.148086 -7.06952,-4.53257e-19 2.16383e-17)) Both of them look like two slightly rotated rectangles, first one being bigger than the other. They intersect at their upper left corner. In order to verify that these polygons CAN be intersected, I ran the following SQL sentence through SQL Server Management Studio (17.9.1): SELECT geometry::STGeomFromText('POLYGON((16.8739 0.353458,8.80872e-14 5.50545e-15,0.266003 -12.6988,17.1399 -12.3454,16.8739 0.353458))', 0) .STIntersection( geometry::STGeomFromText('POLYGON((-4.53257e-19 2.16383e-17,9.99781 0.209424,10.1459 -6.86009,0.148086 -7.06952,-4.53257e-19 2.16383e-17))', 0) ).STAsText() The resulting WKT is: POLYGON ((0.1480860710144043 -7.0695199966430664, 10.145899772644043 -6.8600900173187256, 9.997809886932373 0.20942401885986328, 0 0, 0.1480860710144043 -7.0695199966430664)) which looks about right for the requested intersection rectangle. SSMS itself displays a nice rectangle when you remove ".STAsText()" from that sentence. However, when I tried to duplicate that result using the following program using Visual Studio 2017 (15.9.8) to create an x64 console app, using boost 1.69 as a NuGet: ----------------------------------------------------------------------------------------------------------------- #include <boost/geometry.hpp> #include <vector> #include <iostream> int main(int argc, char** argv) { boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double>> first; boost::geometry::read_wkt("POLYGON((16.8739 0.353458,8.80872e-14 5.50545e-15,0.266003 -12.6988,17.1399 -12.3454,16.8739 0.353458))", first); boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double>> second; boost::geometry::read_wkt("POLYGON((-4.53257e-19 2.16383e-17,9.99781 0.209424,10.1459 -6.86009,0.148086 -7.06952,-4.53257e-19 2.16383e-17))", second); std::vector<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double>>> results; boost::geometry::intersection(first, second, results); for (auto& result : results) { std::cout << boost::geometry::wkt(result) << std::endl; std::cout << boost::geometry::is_valid(result) << std::endl; } return 0; } ----------------------------------------------------------------------------------------------------------------- the resulting polygon is: POLYGON((0 -8.88178e-16,0.148086 -7.06952,0.148086 -7.06952,0 -8.88178e-16)) which you can easily see it's not a valid polygon, even though boost::geometry returns "1" when is_valid() is called upon it. I was planning to use boost::geometry on a large scale server application that processes quite large amounts of geometry in a similar way, and this is seriously impairing my ability to do so. Do you guys know what is going on here, and if there is a solution or workaround for it?

3 7

[release] Boost 1.70.0 Beta 1 is now available
by Marshall Clow 13 Mar '19

13 Mar '19

[ resending with a non-empty subject line ] Boost release 1.70.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.70.0.beta1/source/> The SHA256 checksums are as follows: dbf89645e509acb2e53eac3c633834f1dec80bd8622e6e652a9741dcf0807f17 ./boost_1_70_0_b1.7z 957b984b58656a3ec00661ecad7ef82e3a094bad36e37b9e6624843237854679 ./boost_1_70_0_b1.tar.bz2 76d149c1fb9e8a5ceb3bc1e5587edc40fa79a43e8b990d877c2210f0382b9421 ./boost_1_70_0_b1.tar.gz 71e990b2c26880521fd98459b184ee172ce1c46dcf554b6eaab7776b8b6369a6 ./boost_1_70_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_70_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.70.0 Beta 1 Release Candidate 3
by Marshall Clow 12 Mar '19

12 Mar '19

A new release candidates for the first 1.70.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.70.0.beta1.rc3/source/ Changes since RC2: * Relative paths for --prefix, --libdir, etc. are now bound relative to the current working directory, instead of being relative to the Jamfile. Thanks to Tom Kent for the report, and Steven and Peter for the fixes. Changes since RC1: * The Jamfile for Boost.Predef has been updated to allow running the tests from /status. Thanks to mike.dev(a)gmx.de for the report, and to Rene for the fix. The release notes are not yet available. The SHA256 checksums are as follows: dbf89645e509acb2e53eac3c633834f1dec80bd8622e6e652a9741dcf0807f17 ./boost_1_70_0_b1_rc3.7z 957b984b58656a3ec00661ecad7ef82e3a094bad36e37b9e6624843237854679 ./boost_1_70_0_b1_rc3.tar.bz2 76d149c1fb9e8a5ceb3bc1e5587edc40fa79a43e8b990d877c2210f0382b9421 ./boost_1_70_0_b1_rc3.tar.gz 71e990b2c26880521fd98459b184ee172ce1c46dcf554b6eaab7776b8b6369a6 ./boost_1_70_0_b1_rc3.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. -- The Boost Release Managers

2 3

convert separate year, month, day, hour, minute, secs, ms to milliseconds since epoch
by Victor Yankee 11 Mar '19

11 Mar '19

I am using C++14 and boost 1.64.0 (could move to newest boost), and need to convert date and time pieces to a single value for milliseconds since the epoch. This is what I have: int64_t msSinceEpoch(int year,int month,int day,int hour,int minute,int second,int ms) { struct std::tm t; t.tm_sec = second; t.tm_min = minute; t.tm_hour = hour; t.tm_mday = day; t.tm_mon = month-1; t.tm_year = year-1900; t.tm_isdst = 0; return (1000* timegm(&t))+ms; // is timegm cross-platform? } Is there a better way? Could not figure out how to use boost::chrono :( Something else? Kind Regards, Vic

5 8

SSL handshake: invalid file handle
by Osman Zakir 11 Mar '19

11 Mar '19

I have a problem with using SSL to switch from HTTP to HTTPS in a web server app I have. The code is here:https://github.com/DragonOsman/currency_converter/blob/master/currency… and my server_certificate.hpp file is herehttps://github.com/DragonOsman/currency_converter/blob/master/server_ce…. The app uses Boost 1.69.0, for Boost.Beast. I took synchronous HTTP SSL server example code and synchronous HTTP example client code from the Boost.Beast repository on here. I got the certificate from Let's Encrypt using the TXT record method, and it's a domain-specific certificate. I was told by the guys at Let's Encrypt forums that it doesn't require DH parameters, but I'd like to confirm here if it's true or not. I didn't get DH parameters. It's a certificate issued via acme.sh. The domain name is a subdomain I got for free from dynu.com; the .cer files I have are ca.cer, {DOMAIN}.cer, and fullchain.cer. I was told that I'd need fullchain.cer so I put that in as the value for the `cert` string (it consists of two certificates and I used both). The private key I have is in a .key file rather than a .pem file and I'm wondering if that's a problem. I also need to ask what I need to do with the ctx.set_options and ctx.set_password_callback methods. Could you please help me (if this is good to ask here)? When I try to visit my app in the browser while my server is running (I'm hosting it on my computer), I get this error in my console window: " handshake: The file handle supplied is not valid " And before, I also got this error: " handshake: An operation was attempted on something that is not a socket " And I also get an error page in my browser saying, "Cannot connect securely to this page". I'm using the MS Edge browser. My private key is an RSA key and the filename is {DOMAIN}.key rather than {DOMAIN}.pem. I'm sorry for repeating this. Thanks in advance for any help or replies.

1 0