- Boost - lists.boost.org

boost-install-ing zlib (Was: Re: [Release] Boost 1.70.0 Beta 1 Release Candidate 2)
by Peter Dimov 13 Mar '19

13 Mar '19

> I'll need to try and see what happens with <source> in user-config. > Probably nothing good, because one would expect neither <build-name> nor > <tag> to be specified in such a case. If I remove the check for ZLIB_SOURCE, and just do alias boost_zlib : /zlib//zlib ; libraries-to-install += boost_zlib ; unconditionally in libs/iostreams/build/Jamfile, this is what happens: - when `using zlib : : <source>C:/Projects/zlib-1.2.11 ;` is in user-config, the default `b2 install` fails because `address-model=32,64 variant=debug,release` conflict as all try to build `libz.lib`. When address-model=32 variant=debug is given, `libz.lib` is installed in C:\Boost\lib, and the CMake configuration for boost_zlib correctly points to it. - when using a prebuilt `using zlib : : <include>C:/Projects/include <search>C:/Projects/lib <name>zlib-8 ;`, the CMake configuration file for boost_zlib points to "${_BOOST_LIBDIR}/zlib-8", which is not correct.

2 2

(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 3

[rational] permission to merge cmake change?
by James E. King III 13 Mar '19

13 Mar '19

Before 1.70.0 beta started, some cmake changes from Mike Dev were merged into rational. There was a typo in one of the cmake options (BOOST_RATIONA_INCLUDE_TESTS). This does not affect code nor the boost build system. Would it be okay to merge this now or should I wait? https://github.com/boostorg/rational/pull/35 Thanks. - Jim

1 1

[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

5 8

[Release] Boost 1.70.0 Beta 1 Release Candidate 2
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.rc2/source/ Changes since the last RC: * 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: 26dba8156ad08041c6da52c84a2654aefda292180afe3546a9a74dda0dfb3781 ./boost_1_70_0_b1_rc2.7z ee794d98429bc2bfae054f2fab6fde53ea95f7c5967d8b267e57c894a4d46e57 ./boost_1_70_0_b1_rc2.tar.bz2 bca5f189d87b26ab903838dee2fd4c54e9043bd35d27b8923cdef42651ae7261 ./boost_1_70_0_b1_rc2.tar.gz 6c8f3af4e64d3a04a3d3a5e98499d2f6bb460ad82c1f33ff7da800b5ab182b0b ./boost_1_70_0_b1_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. -- The Boost Release Managers

4 25

Re: [boost] [Boost-users] [release] Boost 1.70.0 Beta 1 Release Candidate 1
by Tom Kent 11 Mar '19

11 Mar '19

On Fri, Mar 8, 2019 at 9:44 PM Tom Kent <lists(a)teeks99.com> wrote: > > > On Fri, Mar 8, 2019 at 8:57 PM Tom Kent <lists(a)teeks99.com> wrote: > >> >> >> On Fri, Mar 8, 2019 at 6:42 PM Marshall Clow via Boost-users < >> boost-users(a)lists.boost.org> wrote: >> >>> On Fri, Mar 8, 2019 at 10:21 AM Marshall Clow <mclow.lists(a)gmail.com> >>> wrote: >>> >>>> The release candidates for the first 1.70.0 beta release are now >>>> available at: >>>> >>>> https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/ >>>> >>>> The release notes are not yet available. >>>> >>>> The SHA256 checksums are as follows: >>>> >>>> a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 >>>> ./boost_1_70_0_b1_rc1.7z >>>> 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 >>>> ./boost_1_70_0_b1_rc1.tar.bz2 >>>> 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e >>>> ./boost_1_70_0_b1_rc1.tar.gz >>>> f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 >>>> ./boost_1_70_0_b1_rc1.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. >>>> >>> >>> >> I'm having a problem with B2 in this release. >> >> For many releases now, I have run a command such as: >> b2 -j16 --build-type=complete toolset=msvc-10.0 address-model=64 >> architecture=x86 --prefix="./" --libdir=lib32-msvc-10.0 >> --includedir=temp_inc install >> >> to get the windows builds of each toolset. For the install, I set the >> prefix as the current directory, so that I'll get a lib{arch}-msvc-{ver} >> directory for each toolset in there. However, with this 1.70 release, it >> seems to ignore my prefix and put the headers in >> libs/headers/build/temp_inc/boost-1_70/boost, instead of >> temp_inc/boost-1_70/boost. For the libraries, it scattered them throughout >> the build in directories such as libs/coroutine/build/lib32-msvc-10.0/. >> >> Any thoughts on what might be causing this? Am I using the --prefix >> --libdir and --inlcudedir correctly? Or at least not badly enough to >> warrant this? >> > > Also, even though I have BZIP2_SOURCE and ZLIB_SOURCE set, I'm not seeing > the appropriate bzip2 and zlib libraries being generated. > > After updating my scripts to us "staging" instead of "install" to avoid the above issue, I was able to get everything else to build successfully for Visual Studio (msvc-10.0 through msvc-14.1, note this is the first release I haven't built against msvc-8.0 and 9.0). The only exception being the lack of bzip2 and zlib support mentioned above. toolset arch compile Link Execute msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. Full build logs can be found at https://gist.github.com/teeks99/0aeed77c9251ba02090d9ab7372e2c73 Tom

4 4

Regarding GSoc 2019
by karmanya grover 11 Mar '19

11 Mar '19

Sir/Madam, I am a Google Summer of Code 2019 aspirant. This email is regarding inquiry of possible projects that I am interested in. Please provide the specifics for following questions. In Boost.uBLAS library, I want to know if there's some work done for python integration previously or not. I also want to inquire about Boost Astronomy library. Looking into git repository, I found that this library is fairly new. What are the aspects hoped to be achieved for this library as a full efficient and mathematical friendly. I have always been interested in Astrophysics and applying those concepts in problem solving. Apart from that, What were the previous works done in Boost.Real library by past GSoc'ers. with regards, Yours sincerely, Karmanya Grover (B.E). NSUT

3 2

[release] 1.70 Windows binaries
by Sean Farrow 10 Mar '19

10 Mar '19

Hi, I know there is a discussion regarding building 1.70 with zlib in another thread, but wondered whether there are any binaries available for msvc without zlib for the 1.70 beta rc1/2? Kind regards Sean.

1 0

[variant2] documentation request
by Andrzej Krzemienski 10 Mar '19

10 Mar '19

Hi Peter, Given that the never-empty guarantee appears to be at the heart of the motivation for boost::variant2, I would suggest to: 1. put in the documentation some motivation behind pursuing the never-empty guarantee. 2. Make it clear that never-empty guarantee is not a strong exception-safety guarantee. 3. Describe the algorithm for achieving the guarantee. The current description does not seem to cover all interesting cases, and I found the behavior quite surprising. For instance, the variant's move assignment will sometimes use T's move assignment rather than move constructor when changing the variant's type, as in the following example: https://wandbox.org/permlink/GDRyS54bpdLP7GVa Regards, Andrzej

10 32

[gsoc19] Seeking Guidance along with mentor for Boost.GIL Project
by Keshav Gupta 10 Mar '19

10 Mar '19

Respected Sir, I am Keshav Gupta currently doing my B.E. in Computer Engineering from Thapar University, Patiala, Punjab, India. Actually I want to participate in GSOC19 and want to work with you during that period. Actually I am interested in implementing various Image Processing algorithms using BOOST.GIL. and I think that I can perfectly work upon this as I am also currently doing my research in the area of Fingerprint Matching and you absolutely know that this definitely includes the usage of image processing algorithms and that why I am interested for this as I know I have the proper knowledge of C++ along with image processing algorithms. Kindly guide me how to proceed further so as to increase my chances of getting being selected in GSOC19. Also please tell me any other way how to contact the mentor of this project as I have mailed him certain number of times but didn't get any response. Waiting for your reply Regards Keshav Gupta

2 1