Re: [boost] Visual Studio 2015 Update 3 has removedstd::unary_functionand std::binary_function

On 11/11/2016 10:57 AM, Rene Rivera wrote:

On Fri, Nov 11, 2016 at 10:18 AM, Edward Diener wrote:

...

On 11/10/2016 9:05 PM, Rene Rivera wrote:

...

On Thu, Nov 10, 2016 at 8:39 PM, Edward Diener wrote:

On 11/10/2016 4:26 PM, Peter Dimov wrote:

...

Edward Diener wrote:

...

is there any documentation on how to setup a Boost submodule for

...

testing using Travis CI ?

The procedure is

1. Add a .travis.yml file in the root of the repository. This file describes what Travis should do.

I do not see anything at https://docs.travis-ci.com/ that gives the details of the .travis.yml file so that I can create an appropriate one for a Boost library. If it exists it is well-hidden on the website.

You can look at other Boost libraries for examples. Although I'm also working on a general .travis.yml file that any library can use with some common scripts that will eventually integrate with the general Boost test regression results reports. For that you can copy the one from Predef < https://github.com/boostorg/predef/blob/develop/.travis.yml>. Literally copy-paste and minor edits for that one.

Looking at the .travis.yml in predef, other than the 'notifications:' section, is the file meant to work with any Boost library and travis CI ? Also the appveyor.yml in predef, other than the 'notifications:' section, looks like it is supposed to work with any Boost library for appveyor. Is that also the case ?

Yes that is the intent. I went under the true and tried plan that the less work someone has to do the more likely they are to do it :-)

Agreed !

Although there are other things you can do.. Like remove some of the toolsets being tested. As the list for Predef is maximal for both testing all the options for the CI script and for Prefef which is all about detecting variations in toolsets.

I can see the toolsets listed. For the .travis.yml it does not appear that the many of the latest clang and gcc are there. How do you know what toolsets travis CI actually contains for testing ? For gcc 5.1 is pretty old compared to 5.2, 5.3, 5.4, 6.1, 6.2. For clang there exists 3.7, 3.8, and 3.9 which has been officially released. The appveyor.yml does list the major releases of VC++ I usually test against on Windows ( I can also manually test against VS2005 ), but probably compliance from VS2008 and VS2010 should not be expected for many libraries.

...

Or am I supposed to massage the script.py for a different library ( I know Python ) ?

I sure hope not. But if you find you need to do that we should discuss what you need so that I, or someone else, can account for it as we move forward with the modular CI testing system.

If I don't need to modify it to test other Boost libraries I am fine with it.