- Boost - lists.preview.boost.org

General Advice Thankyou - now I need a Trac login
by Fletcher, John P 14 Feb '14

14 Feb '14

Thank you for the helpful responses and a lot of new information. I now need a trac login and to be assigned as the maintainer for Phoenix. I have not found instructions for getting a Trac login. Please help. John

3 4

path of test-binary
by dib 14 Feb '14

14 Feb '14

Hi, within the tests of a (not-yet) boost-library, how can I find out the path where b2 placed the binaries of the tests? Problem is the following: Some of the tests need the path to a shared library, which is built together with the tests. In the lib/mylib/tests/Jamfile.v2 I have the following: [...] # our test lib for shared library tests lib test_library : test_library.cpp ; test-suite mylib : # # shared library # [ run shared_library_load_test.cpp ] [ run shared_library_get_symbol_test.cpp ] # # [...] Inside shared_library_*_test.cpp I need something like this: boost::filesystem::path tstlib("bin.v2/libs/mylib/test/mycompiler/test_library.so"); As boost.build decides by itself where to put the binary, i cannot hardcode the path in the source-files.. Is there a way to get the path from boost.build? If not, how could I solve this problem? -- regards dib

2 1

[git] automated update of superproject master branch
by Peter A. Bigot 14 Feb '14

14 Feb '14

I realize there are several email threads about how the super-project branch should be managed, but most pre-date live experience with boost on git and go deep into other aspects of the issue, so I still want to call this out specially: https://svn.boost.org/trac/boost/wiki/ModBigPicture specifies that the master branch on each module should be stable at all times, which is the right policy. Currently, the master branch on the super-project is automatically updated twice(?) per hour selecting all updates to the master branches of modules. Consequently, super-project master is the exact opposite of stable. This divergence is confusing. I'm unconvinced that waiting a few days will demonstrate a significant decrease in churn on the super-project master branch. Some is due to multiple updates to specific modules, which might decrease as maintainers become more familiar with git and only push once, but interoperability issues will still arise and there will be no way to tell which master branch commits produce a working Boost installation. There is value in having a branch with automated-update semantics, but IMO regardless of what the final policy will be, "master" is not the right choice for this, and automated updates of it should stop ASAP. Perhaps the update script can simply be moved to occur on latest/master and latest/develop. Leave master untouched until whatever gets committed to it has undergone cross-toolchain integration validation, and make develop available for changes to superproject content that are not just submodule updates. Peter

4 4

General advice needed for new maintainers.
by Fletcher, John P 14 Feb '14

14 Feb '14

I have been maintaining Boost Phoenix for several weeks. To start with I was mainly attempting to fix as many bugs as possible and also sorting out things like missing copright and licence. I am now up to the more difficult bugs which take longer to fix. I also need some more information and some actions which I cannot take myself. I have asked about a number of these on this list and I am lacking answers to a good many of them, so I am going to summarise them here. I think it would be a great help to people undertaking maintenance for the first time, without having first been an originator of a library if some guidelines were in a document. 1. General guidelines on the responsibilities of a maintainer and who is responsible for the elements outside the developer's control. In particular, what happens when there is a release of boost? 2. General guidelines on the responsibilities for bugs and who to contact if a bug seems to be due to a different library. 3. Guidelines on the use of trac and how to get given the ability to record bugs as now fixed. 4. Where is the archive for boost-bugs? It would be useful to look at past fixes to find out what has gone on. Someone suggested searching but I cannot search until I know what is there. 5. A list of who is maintaining what. 6. Documentation. I am trying to get to grips with boostbook and quickbook. Some libraries are included in a section with indexed chapters and some are not. Is there a policy about this. When I asked how Phoenix could join the only reply I had was not to bother. Is there a documentation policy? It would be good to be able to generate the web pages myself to check them when I am making changes, which may be substantial. 7. More technical. How are things to be handled in relation to C++11. (a) Things which used to work which now don't with C++11? (b) Things which only work with C++11? (c) and what about C++14? I am fixing things in an adhoc way but it would be good to have a uniform approach. 8. Boost predef for version numbers. I have introduced this into Phoenix alongside the existing method. 9. Changelog. As a user I have found this useful in libraries I have used elsewhere, so I have put one into Phoenix following the style I found in wave. There is quite a lot here, but it has been building up for some time as I find I need more information to work effectively. John Fletcher P.S. Thanks to all those who have helped me get this far.

3 3

Interested in working with Boost C++ Libraries
by Arpit Sharma 13 Feb '14

13 Feb '14

Hello, My name is Arpit Sharma. I'm a 3rd year Computer Science student. I'm very much interested to work for Boost C++ Libraries in Gsoc 2014 and would like to work after that also. Any pointers on how to proceed. -Thank you, Arpit Sharma

2 1

Contributing to Boost as a part of GSoC 2014
by Kamal Gurala 13 Feb '14

13 Feb '14

Hi All, My name is Kamal Gurala, I am currently pursuing a B.tech in CSE from IIIT-Hyderabad ( India ). I have a good knowledge of C++, Data Structures, and Algorithms. I want to get started with contributing towards Boost. I would be obliged if any one could help me in this regard. Regards, Kamal Gurala

2 1

[fusion.adapted.std_tuple] bug
by Hui Li 13 Feb '14

13 Feb '14

Looks like 2 files share the same include guard macro definitions. This makes it very hard to use Boost.Fusion for std::tuple's, especially if both boost::tuple and std::tuple need to be adapted. mbpro:fusion huil$ find . -type f |xargs grep -w BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726 ./adapted/boost_tuple/detail/category_of_impl.hpp:#if !defined(BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726) ./adapted/boost_tuple/detail/category_of_impl.hpp:#define BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726 ./adapted/std_tuple/detail/category_of_impl.hpp:#if !defined(BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726) ./adapted/std_tuple/detail/category_of_impl.hpp:#define BOOST_FUSION_CATEGORY_OF_IMPL_09272006_0726

2 1

How to add a library to the BoostBook Documentation Subset?
by Fletcher, John P 12 Feb '14

12 Feb '14

I have taken over the task of maintaining Boost Phoenix. I want to start expanding the documentation which already uses Quickbook. The BoostBook Documentation Subset here includes a lot of libraries but not Boost Phoenix. http://www.boost.org/doc/libs/1_55_0/doc/html/index.html How do I get Boost Phoenix added, and are there any requirements for the documentation which need to be observed? Thanks John Fletcher

2 1

Building a new boost library in Google summer program!
by Khaled Ammar 12 Feb '14

12 Feb '14

Hi everyone, I'm new to this list so please excuse my lack of experience. I'm interested to build a boost library as part of Google Summer of Code ( http://www.google-melange.com/gsoc/homepage/google/gsoc2014) Could you please advice me who should I contact? -- Thanks, -Khaled Ammar PhD student at Uwaterloo www.khaledammar.com

3 2

Warning.. Regression testing changes forthcoming..
by Rene Rivera 12 Feb '14

12 Feb '14

We, mostly Ahmed Charles, will be moving the regression and release script code to independent git repos (i.e. moving the out of the boost super-repo). The first step is to copy the git histories. This requires that NO ONE make changes to the regression and release code. This first step will happen tonight at 8-12 pm PST. Further actions for testers to take will follow in the next 2-3 days. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

1 0