- Boost - lists.boost.org

1.58.0 rc3 is now available
by Marshall Clow 12 Apr '15

12 Apr '15

Release candidate files for 1.58.0 are available at: http://boost.cowic.de/rc/ * Since rc1, the changes that were causing the serialization libraries to fail to build on MSVC have been reverted. * Since rc2, the documentation for bind, and mem_fun. No code changes. 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. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost_1_58_0_rc3.7z) = f7255aeb692c1c38fe761c32fb0d3ecd MD5 (boost_1_58_0_rc3.tar.bz2) = b8839650e61e9c1c0a89f371dd475546 MD5 (boost_1_58_0_rc3.tar.gz) = 5a5d5614d9a07672e1ab2a250b5defc5 MD5 (boost_1_58_0_rc3.zip) = b0605a9323f1e960f7434dbbd95a7a5c Thanks! -- The release managers P.S. Release notes are here: http://www.boost.org/users/history/version_1_58_0.html

3 3

[serialization][develop] Unable to find file or target named 'test_polymorphic_helper.cpp'
by Dmitry Moskalchuk 11 Apr '15

11 Apr '15

It seems that latest commit to develop branch of Boost.Serialization (https://github.com/boostorg/serialization/commit/a32549c25fa983fea2b5dfeaf9…) break build of Boost: error: at /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-v7a-develop/test/develop/regression/armeabi-v7a/test/boost_bb/src/kernel/modules.jam:107 error: Unable to find file or target named error: 'test_polymorphic_helper.cpp' error: referred to from project at error: '../libs/serialization/test' And really, there is no file libs/serialization/test/test_polymorphic_helper.cpp. I guess it was forgotten to be added to git. -- Dmitry Moskalchuk

2 1

[Boost Document Library] Which SDK / OS to use for development?
by Abhinav Tripathi 11 Apr '15

11 Apr '15

I am trying to start the development of a Document Library for Boost which was listed under the GSoC projects list. I successfully built Boost 1.57 on windows 8 with MinGW using some help from this mailing list. Now, i wish to develop the library on windows only (Although i can shift to linux if need be).... When i went through the links provided on the ideas list, i came across following things : --The OpenOffice SDK asks to either use linux or Visual Studio on Windows and there is practically nothing (documentation) for compiling with MinGW. --The LibreOffice SDK also asks to install many *nix tools first and also doesn't mention anything about compatibility with MinGW. --The last 2 links use .NET and some other MS libraries which i am pretty sure won't be much portable... . I wish to develop the library so as to get it accepted to Boost at some point. I assume that Boost would accept only cross platform code, so i discarded the last two links. I am now in a dilemma..... Which of the 2 SDK should i try to use on Windows with MinGW.. Or should i NOT develop on windows and shift to linux... . Also, The MS Office formats are not open but other office formats might be open and hence i can also try and develop something without using any of the available SDKs. So, instead of developing of a wrapper, i can aim to develop a complete library to load and manipulate document files... . Please suggest some option and show me a way as to which SDK/Platform should i use. And how to continue the development for the Document Library. . Regards, Abhinav

2 3

[fiber, afio, dl, bindlib, expected, hana, tick, fit, simd, dispatch] Checking my shortlist of upcoming Boost C++ 11/14 librari
by Niall Douglas 10 Apr '15

10 Apr '15

Dear Boost, I've spent the last few days reviewing the shortlist of C++ 11/14 libraries as suggested in this thread http://article.gmane.org/gmane.comp.lib.boost.devel/255548 which appear closest to entering Boost as per the rules in my C++ Now abstract: 1. The library must be C++ 11/14 only. As in, no C++ 03 compilation possible. 2. The order chosen shall be the closest to entering Boost in March/April (i.e. now), so already in Boost, approved to enter Boost, in the formal review queue, approaching the formal review queue. At https://drive.google.com/open?id=1Bizs9xz2dyt1d5GJv-pOCmu1cS67gRd0KNYn sjYK Ji w&authuser=0 you will hopefully find a traffic light dashboard spreadsheet (I tried posting a PNG here, it was refused). In it is shown the current state, as estimated by fallible me from a cursory glance at the library, for various measures of the library. Errors are entirely possible, hence me asking here before I make a fool of myself. List members may be as surprised as I was to learn that most of the upcoming libraries require C++ 14. They are also universally standalone from Boost, being about as weakly dependant as is possible and still be called a Boost library. That was a big surprise to me as well. Another surprise was the dislike of Boost.Test - a lot of libraries don't use it, indeed can't use it. And finally, almost everyone uses Travis CI, though not valgrind memcheck for leak detection nor coveralls for unit test coverage. The first category is libraries already in the formal review queue or better. These are: Fiber, AFIO, Dl. The second category is libraries where the authors have been visible enough for me to review the library and score it onto the dashboard. These are: BindLib, Expected, Hana, Tick, Fit. ... of which BindLib, Expected and Hana are the most "Boost ready" by my estimation. I still haven't reviewed Sqlpp11, SIMD, Dispatch, Range v3, Spirit X3 nor Proto 0x. The main reason why not is that I would never use any of those libraries in any work I expect to do anytime in the next five years. That's quite unfair to those libraries, but I have another big reason: I'm also hesitant to review libraries covered by their authors also present at C++ Now, or have presented on them in the past, as it won't add value plus I probably wouldn't know what I'm talking about compared to them so that removes Expected?, Hana, SIMD, Dispatch, Range v3, Spirit X3 and Proto 0x. Which leaves a shortlist of: Fiber, AFIO, Dl, BindLib, maybe Expected, maybe Tick and Fit. I think SIMD and Dispatch have been presented on before at C++ Now right? Could anyone also very quickly summarise the main differences in their C++ 11 only rewrite? I think I remember it was mainly compilation speed rather than doing anything unusually C++ 11 only? Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

4 4

[peer review queue tardiness] Cleaning out the Boost review queue
by Niall Douglas 10 Apr '15

10 Apr '15

I've been reviewing the Boost Formal Review queue as part of preparing my C++ Now presentation and I observe the following things: Observation 1. The following review submissions have not been updated by their authors in over two years and therefore count as unmaintained. Abandoned libraries before peer review are even more undesirable than abandoned official Boost libraries, I therefore suggest they be removed from the review queue until their authors bring them up to date: * Join (last update 2009) * Block pointer (last update: well, it's still in the SVN sandbox) * Singularity (last update 2011) * Extended Complex Numbers (last update 2012) * Array (last update 2012) * Countertree (last update 2012, I see a github import in 2013 but no new commits) * Process (last update 2012). This is a particularly useful library I have used myself in production code, and I see a number of mirrors of it on github each with varying patches and bug fixes. As a minimum, somebody needs to create a canonical github project for Process and merge the fixes from the many github copies. Otherwise, I'm sorry but this library needs to be considered abandoned otherwise, and removed from the review queue. It may be the case that the links on the review queue wiki page are simply out of date. If so, they need to be updated. Otherwise a purge of the queue is very desirable such that the queue accurately reflects ready to use new Boost libraries. Observation 2: Edit Distance (Algorithm) by Erik Erlandson shouldn't be in the queue. What he's done is to add a new algorithm to Boost.Algorithm, so the maintainer for Algorithm (Marshall?) should either merge his contribution or reject it as inappropriate or badly implemented. Failing that, Edit Distance should be spun into a standalone library instead of forking Algorithm. Right now it is supplied quite literally as a fork of the algorithm github. It should be a pull request, yet I don't see it in the pull requests for boostorg/algorithm, neither open nor closed. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

15 43

[AIX6.1] [64bit] [build boost 1.57] Help required to build boost
by 임영운 10 Apr '15

10 Apr '15

hi, I'm newbie. the only one thing that I wanted to ask is building boost 64bit on aix6.1. I try it a number of times. and I failed building 64bit boost objects. It built only 32bit objects. would you tell me how to build boost 64bit on aix6.1 thanks read this msg. 주식회사 테미 임영운(Yeong-woon Im) 305-764 대전광역시 유성구 대학로99 충남대학교 산학연교육연구관 807호 #807, TBI Center, Chungnam University 99 Daehak-ro, Yuseong-gu, Deajeon, 305-764 Korea Home URL : http://www.temee.co.kr Tel : 042-824-7014 Fax : 042-824-7015 Mobile : 010-6266-9960

2 1

Re: [boost] [Boost-users] 1.58.0 rc3 is now available
by Marshall Clow 09 Apr '15

09 Apr '15

On Thu, Apr 9, 2015 at 4:11 AM, Deniz Bahadir <dbahadir(a)benocs.com> wrote: > Building Boost 1.58.0-rc3 succeeded only partially. > > > Success: > > Debian 7 with GCC 4.8.2 (in C++03 mode) with build-command: > b2 -j4 --build-dir=/opt/build/test --build-type=complete > --layout=versioned address-model=64 architecture=x86 install > --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" > cxxflags="-fPIC" dll-path="/opt/test/lib/x86_64-linux-gnu" > > > Failure: > > Debian 7 with GCC 4.8.2 (in C++11 mode) with build-command: > b2 -j4 --build-dir=/opt/build/test --build-type=complete > --layout=versioned address-model=64 architecture=x86 install > --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC > -std=c++11" dll-path="/opt/test/lib/x86_64-linux-gnu" > > > The main-error seems to come from "Boost.Context" and the use of unknown > "std::index_sequence": > > std::index_sequence is a C++14 feature. -- Marshall

1 0

[language] determine sence of language proposal concerning the 'default'-keyword
by Jakob Riedle 09 Apr '15

09 Apr '15

Hello boost community, since this seems to me kind of a proving ground for new C++ library/language features I'd ask this question here. Would you recon' writing a language proposal about: using the 'default'-keyword as some standard way of calling the default ctor of variables. I could imagine the following use-case: void foo( some::very_long_name<some_very_long_template_param> arg = default ){ return; } This would make things shorter, in the way 'auto' does it for types. You could also do it for passing parameters: foo( default ); This could interact very well with boost::optional, make it more intuitive and easier to use: optional<int> bar( optional<some_long_type_name> arg = default ){ return default; } bar( default ); This way, you don't have to write 'optional<some_long_type_name>()', both at the parameter and at the function call. What do you think of such a language proposal? Regards, Jakob Riedle

5 5

[MinGW] [Windows] [build boost 1.57] Help required to build boost
by Abhinav Tripathi 08 Apr '15

08 Apr '15

I had submitted a GSoC application regarding developing a document library for boost and i wanted to do something regardless of the results of selection. . SO, i downloaded boost 1.57 source and tried to build it using MinGW compiler that i downloaded with CodeBlocks IDE which i use. When i ran : bootstrap.bat gcc I got error "Failed to build Boost.Build Engine". . The bootstrap.log file was : ### ### Using 'gcc' toolset. ### E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>if exist bootstrap rd /S /Q bootstrap E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>md bootstrap E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>gcc -DNT -o bootstrap\jam0.exe command.c compile.c constants.c debug.c execcmd.c execnt.c filent.c frames.c function.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c object.c option.c output.c parse.c pathnt.c pathsys.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c md5.c class.c cwd.c w32_getreg.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>.\bootstrap\jam0 -f build.jam --toolset=gcc "--toolset-root= " clean ...found 1 target... ...updating 1 target... ...updated 1 target... E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>.\bootstrap\jam0 -f build.jam --toolset=gcc "--toolset-root= " ...found 159 targets... ...updating 3 targets... [MKDIR] bin.ntx86 'C:\Users\Abhinav' is not recognized as an internal or external command, operable program or batch file. md "bin.ntx86" ...failed [MKDIR] bin.ntx86... ...skipped b2.exe for lack of bin.ntx86... ...skipped bjam.exe for lack of b2.exe... ...failed updating 1 target... ...skipped 2 targets... . . I am NOT any expert but as far as i can guess, it tried to execute "C:\Users\Abhinav" which ofcourse is NOT any valid command... . How can i build boost? Is there a way to use it without actually building the source? Please help! . Regards, Abhinav

2 2

Is boost.python dead?
by Mikhail Matrosov 08 Apr '15

08 Apr '15

Hello, I made a pull request for boost.python: https://github.com/boostorg/python/pull/15 Two weeks passed since then and I had no reaction still. Did I do something wrong? I see no pulse for the project. Is it alive? Is there a way to find out its status? The last meaningful commit is dated back to 7 Dec 2012. ----- Best regards, Mikhail Matrosov

5 7