August 2015 - Boost - lists.preview.boost.org

[http] Formal review starts on Friday
by Bjorn Reese 05 Aug '15

05 Aug '15

This is a short notice that the formal review for the Boost.Http library starts on Friday and will last for ten days: from August 7th until August 16th. A proper announcement will be made on Friday, which will include links to the source code and the documentation to be reviewed. As a courtesy to the ASIO community we encourage your participation in the formal review as well.

2 1

[1.59] SVG's not showing up in beta
by John Maddock 05 Aug '15

05 Aug '15

SVG graphics used in documentation are still absent from the (beta) website, see for example: http://www.boost.org/doc/libs/1_59_0_b1/libs/math/doc/html/math_toolkit/sf_… I assume a script somewhere needs updating? Thanks, John.

2 2

Trying out QVM with multiple library implementations
by Andrew Hundt 05 Aug '15

05 Aug '15

I'd really like to try out QVM because I have to switch between a half dozen matrix, vector and quaternion types constantly and would prefer not to write functions for each conversion and operations between them. Examples of the formats I need to handle are: *Eigen <http://eigen.tuxfamily.org/index.php?title=Main_Page>:* Eigen::Affine3d Eigen::Quaterniond + rotation and translation versions *vrep <http://www.coppeliarobotics.com/helpFiles/en/apiFunctions.htm#simBuildMatri…>:* float[3] (vrep vector) float[4] (vrep quaternion) float[12] (vrep homogeneous transform matrix) *cisstVector <https://github.com/jhu-cisst/cisst/tree/master/cisstVector>:* vctDynamicVector <https://github.com/jhu-cisst/cisst/blob/master/cisstVector/vctDynamicVector…> vctQuaternion <https://github.com/jhu-cisst/cisst/blob/master/cisstVector/vctQuaternion.h> vctDynamicMatrix <https://github.com/jhu-cisst/cisst/blob/master/cisstVector/vctDynamicMatrix…> There are also fixed versions of the "Dynamic" objects. + rotation & translations Is there any particular concerns I need to take regarding alignment, ordering (row vs column major) etc? For example, the ordering of the quaternion data components differ between eigen and rep: // 0123 // vrep quat is ordered xyzw, // eigen quat is ordered wxyz Any advice on how to go about this would be appreciated so I can try QVM out! Cheers! Andrew Hundt

2 1

Broken links in 1.58.0 release notes
by Jonathan Wakely 04 Aug '15

04 Aug '15

At http://www.boost.org/users/history/version_1_58_0.html the release notes on the breaking change for Variant say "See get.hpp and polymorphic_get.hpp descriptions for more info" but both hyperlinks are broken.

2 1

Review Request: QVM (generic Quaternion, Vector and Matrix operations library)
by Emil Dotchevski 04 Aug '15

04 Aug '15

Boost QVM defines a set of generic functions and operator overloads for working with quaternions, vectors and matrices of static size. The library also defines vector and matrix data types, however it allows users to introduce their own types by specializing the q_traits, v_traits and m_traits templates. Online documentation and a link to download the source code under the Boost license is available at http://www.revergestudios.com/boost-qvm/. I would like to thank Adam Wulkiewicz for volunteering to be the review manager for QVM and for his valuable initial feedback. Thanks, Emil Dotchevski

13 30

BOOST_NO_CXX11_CONSTEXPR and msvc-14.0
by Peter Dimov 04 Aug '15

04 Aug '15

I see that BOOST_NO_CXX11_CONSTEXPR is no longer being defined for msvc-14.0. Even the RTM version has spotty support for constexpr though; the techniques in my metaprogramming article, for example, don't work. One simple example that fails is #include <type_traits> template< int I > struct X { }; template<class... T> constexpr int f( T... t ) { return 1; } template< class... T > struct Y: X< f(std::is_same<T, void>::value...) > { }; Y<void, void, void> y; int main() { } Another is #include <type_traits> template< class... T > struct X { static constexpr bool v[] = { std::is_same<T, void>::value... }; }; int main() { }

15 32

[serialization] Errors when testing withe mingw-64/gcc on Windows
by Edward Diener 04 Aug '15

04 Aug '15

When running serialization tests with mingw-64/gcc on Windows I get repeated errors of the form: ..\..\../boost/archive/detail/basic_oarchive.hpp:64:5: error: function 'boost::archive::detail::helper_collection& boost::archive::detail::basic_oarchive::get_helper_collection()' definition is marked dllimport get_helper_collection(){ Is this a known problem ? Testing with VC++ does not give any errors.

2 5

Boost 1_59_0_b1_rc1 is available for testing
by Marshall Clow 02 Aug '15

02 Aug '15

Release candidate files for 1.59.0 beta 1 are available at http://boost.cowic.de/rc/ 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_59_0_b1_rc1.7z) = f54a97e5ee7f8e3d04cd9af8396e30f9 MD5 (boost_1_59_0_b1_rc1.tar.bz2) = 9804305aae0c9de9f8cfc02e3de75167 MD5 (boost_1_59_0_b1_rc1.tar.gz) = e584770bd76885c123a0426d24466fe2 MD5 (boost_1_59_0_b1_rc1.zip) = ee34f223aa789a6b3f727cb9480651ed Thanks! -- The release managers

13 14

[Log, Filesystem] Build errors using B2 and Jamfiles distributed with Boost
by Norbert Wenzel 02 Aug '15

02 Aug '15

I'm a lazy guy so I try to use Boost.Build whenever I can. That way I can simply download the Boost tarball, extract it into my project's directory and use the Jamfiles distributed with Boost. Recently I switched to 1.58 and my project setup failed to build, complaining that Filesystem would be built twice with different settings* (actually it would be built one time without any specific settings and one time with a sane set for my platform). I managed to create a "simple" project setup to reproduce this error. I created a library (testlib) with a single extern C function that fills a user provided buffer with the current working directoy. This library uses Boost.Filesystem internally. Therefore the lib's Jamfile also references the Jamfile distributed with Filesystem. I created an executable (test) that calls the lib function and also uses Filesystem to get the parent directory of the current working directory (as reported by the lib function). This setup builds fine as long as I use cout to write the paths in the test exe. When I replace cout with Boost.Log (and therefore also reference the boost_log and boost_log_setup projects) this setup only builds with Boost 1.57. From 1.58 on (also tested with 1.59.b1) the project does not build because Filesystem would be built twice with different settings. Since the error can be triggered by changing the Boost version I reckon this is due to a change in one of the Jamfiles (probably Boost.Log) and not a problem of Boost.Build per se. But for reference I use Boost.Jam Version 2014.03 (the one distributed with 1.58). Since the "simple" setup consists of a few files and directories I've made it available via Github: https://github.com/norbertwenzel/boost-build-problem I've posted this here and not to Boost.Build ML since I suspect this is due to a change in one of the two libraries mentioned and not a bug or misuse in/of Boost.Build. Any help appreciated. thanks, Norbert *) The exact error message I got: error: Name clash for '<p/tmp/b2_problem/external/boost_1_58_0/bin.v2/libs/filesystem/build/gcc-5.1.0/debug>libboost_filesystem.so.1.58.0' error: error: Tried to build the target twice, with property sets having error: these incompatible properties: error: error: - none error: - <abi>sysv <binary-format>elf <log-api>generic <preserve-test-targets>on <python-debugging>off <python>2.7 <testing.execute>on <threadapi>pthread error: error: Please make sure to have consistent requirements for these error: properties everywhere in your project, especially for install error: targets.

2 3

[http] Scheduling a review for Boost.Http
by Bjorn Reese 01 Aug '15

01 Aug '15

I am about to schedule a formal review for Boost.Http (see blincubator for links.) If there are no objections I suggest that the review is held from August 17 to 30.

3 4