- Boost - lists.preview.boost.org

[gsoc19] Seeking a mentor for Boost.Geometry project related to triangulation and random sampling
by Tinko Bartels 01 Apr '19

01 Apr '19

Hi, I am interested in participating in this year's Google Summer of Code with a contribution to Boost.Geometry. I am looking for mentors and I understand that potential mentors for Boost.Geometry-related projects are Vissarion Fysikopoulos and Adam Wulkiewicz. My proposal is a project that is based on project 3 and 4 for Boost.Geometry in the Wiki. I propose to add concepts for triangles, triangulation, and point-generators for random sampling, as well as corresponding models and an algorithm for Delaunay-triangulation with parametrizable geometric predicates. The first draft of my proposal can be found here: https://docs.google.com/document/d/17M44Hpn0KMuECztCbkvTYIeN2EiXbMAUsVni22K… My implementation of the tasks in the competency tests can be found here: https://tinko92.github.io/boost_geometry_GSoC_2019_project_3_4_test/ I'd be thankful for any feedback. Kind regards, Tinko Bartels -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

3 10

[gsoc 2019]proposal to Boost.GIL project 1
by raghuchandra kanakamedala 01 Apr '19

01 Apr '19

Hi Please give me your feedback on my proposal to increase my chases of participation in the project. link: https://docs.google.com/document/d/1-BZO0VuIcebe1ZcdyxHGjOEkQL3eeaXwGtKCWyQ… Thank you K RaghuChandra

1 0

[GSOC 19]Boost.GIL
by raghuchandra kanakamedala 01 Apr '19

01 Apr '19

Hi Is there a mentor for Boost.GIL.If so please send me his/her email id. Thanking you K RaghuChandra

1 0

[format] Allow the format library to use std::optional
by Sean Farrow 30 Mar '19

30 Mar '19

Hi, Would be possible/desired to allow boost.format to use std::optional instead of boost.optional when compiling a C++17 project. I've raised a GitHub issue to resolve this: https://github.com/boostorg/format/issues/63 I would be happy to do this if it were warranted. Kind regards Sean.

1 0

Re: [boost] [Boost-build] Building Boost 1.69 with Visual Studio 1.69
by Steven Watanabe 29 Mar '19

29 Mar '19

AMDG On 3/27/19 12:02 PM, Paul Bristow wrote: >> <snip> > I was fully up-to-date on develop yesterday, and installed git a week ago (new machine ;-) ). > The current revision of Boost.Build in develop should be e22a75c8 (March 18) > I am also slightly concerned that specifying the cl.exe fully may not be updated when Visual studio is updated, as happens today? > But it does seem to using the new compiler version, even though the full cl.exe file specification is no longer correct. > Similarly vsvarsall.bat location in the set command will change. > > But I am getting Boost library files built OK for several compilers and versions, so that's progress. > Hmm. It looks like VS2019 isn't being autodetected. It seems to be working for Tom's test runners. Maybe see what you get from: vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath -version "[16.0,17.0)" (This is how Boost.Build tries to detect VS2019.) In Christ, Steven Watanabe

6 12

Regarding BOOST.Astronomy
by Sarthak Singhal 29 Mar '19

29 Mar '19

Hello everyone, I am not able to understand what exactly is to be done to complete the parser for FITS and I have also tried understanding the codebase but I am not getting what is the work done till now. Can you also provide some resources? Thanking you Sarthak Singhal

4 3

[visibility][test][osx] visibility warnings with 1.70beta
by Raffi Enficiaud 28 Mar '19

28 Mar '19

Hi, I have a side project that requires boost.test and I thought it is the right time to use the beta build of 1.70. At link time for my project (in this case a simple boost.test module), I have tons of warnings like the following: ld: warning: direct access in function 'boost::unit_test::decorator::depends_on::apply(boost::unit_test::test_unit&)' from file '/Users/raffi/from-big-laptop/code/software_workshop/sw_thirdparties/osx/boost_1_70_0_b1/lib/libboost_unit_test_framework-xgcc42-mt-x64-1_70.a(decorator.o)' to global weak symbol 'boost::unit_test::basic_cstring<char const>::null_str()::null' from file '/Users/raffi/code/mpi/mpi_kmeans/build/MPI-Kmeans.build/Debug/test_mpi_kmeans.build/Objects-normal/x86_64/test_cls_and_func_impl.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings. running Xcode 10.1 on 10.14/mojave. I am building boost like this: ./b2 \ cflags="-mmacosx-version-min=10.10" \ cxxflags="-std=c++11 -stdlib=libc++ -mmacosx-version-min=10.10" \ mflags="-mmacosx-version-min=10.10" \ mmflags="-mmacosx-version-min=10.10" \ linkflags="-stdlib=libc++ -mmacosx-version-min=10.10" \ --prefix=`pwd`/../${build_folder} \ --without-log \ --layout=versioned \ install Each of the files that are being built in my project and that are raising the warning have a compilation command like this: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -DBOOST_ALL_NO_LIB -DKMEANS_VERBOSE=0 -I/Users/raffi/code/mpi/mpi_kmeans/include -I/Users/raffi/code/mpi/mpi_kmeans/applications/include -isystem /Users/raffi/from-big-laptop/code/software_workshop/sw_thirdparties/osx/boost_1_70_0_b1/include/boost-1_70 -O3 -DNDEBUG -std=gnu++11 -o CMakeFiles/test_mpi_kmeans.dir/test/test_kmeans.cpp.o -c /Users/raffi/code/mpi/mpi_kmeans/test/test_kmeans.cpp which is pretty much what I had so far and before 1.70. Boost.test is using BOOST_SYMBOL_VISIBLE to make a symbol public, including the static build variant. Why does the linker say """ This was likely caused by different translation units being compiled with different visibility settings. """ is completely unclear to me. How can I inspect what b2 emits as compilation command line for further debugging? All those visibility issues are causing me a lot of headache :) Thanks! Raffi

3 5

Gsod19 interest
by Damian Vicino 27 Mar '19

27 Mar '19

I'm wondering if there is interest to make boost participate in the Google season of docs. The program is similar to Google summer of code in many ways, but the outcome is production of documentation. It Details: g.co/seasonofdocs <https://developers.google.com/season-of-docs/>

5 15

[GSOC 2019]
by shehab alaa 27 Mar '19

27 Mar '19

Hi, I’m student willing to participate in GSOC 2019. I have finished my competency test for Boost.uBLAS and I have interest in projects 2 (Adding new numerical linear and multilinear algebra algorithms).So I’m writing looking for mentor who have interest to guide me. And here is my GitHub link for competency test https://github.com/Shehabalaa/CompetencyTest Best regards, Shehab Alaa

2 1

Re: [boost] [review][variant2] Variant2 Review Starts April 1
by dariomt＠gmail.com 26 Mar '19

26 Mar '19

> > The class boost::variant2::variant<T...> is an almost conforming > implementation of std::variant with the following differences: > I see the useful comparison to std::variant in the doc, however I'm using boost::variant extensively in my code. It would be very useful to have also a short comparison to boost::variant in the doc, as I would expect many more current users of the venerable boost::variant than of its much younger cousin std::variant. Thanks!

6 8