Re: [boost] [MPL] A Proposal

On Mon, Nov 14, 2016 at 12:06 AM, Edward Diener wrote:

On 11/13/2016 11:40 AM, Bruno Dutra wrote:

...

On Sun, Nov 13, 2016 at 3:34 PM, Edward Diener wrote:

[snip]

...

Even if someone were to write a C++ library which needs only basic C++03 compliance to work properly I think he would still want to promote the library as working on the latest versions of popular compilers ( gcc, clang, VC++ ) rather than much older releases.

I suppose you refer to the compatibility status table [1]? Do you think it would be better not to mention the exact minimum versions that are tested and known to work with Metal?

I think it would be better to list all the versions that you have tested and which you know are working properly. I don't mind minimum versions but I did not understand from it that you are implying that all later versions have been tested and should work with Metal.

Thanks for your feedback, I'll be sure to make it explicit from the User Manual that Metal is tested on newer compiler versions as well [1]. On Sun, Nov 13, 2016 at 11:52 PM, Edward Diener wrote:

On 11/13/2016 9:42 AM, Rene Rivera wrote:

...

For Travis you can choose to use Trusty, ie Ubuntu 14. And you can use it in non-container mode. And you can turn on sudo support. And hence can install whatever you like from sources or packages. Which is what Predef does for testing the almost dozen compiler versions on Travis.

Where is there information on Travis CI about which compiler versions are available

I think in the particular case of C++ on Travis CI it is kind of implicit that you should take care of installing whatever development tools fit your needs. To make this easy for the developer, they make it possible for the user to specify 'sudo: required', which basically provides easy access to the various package repositories available to Ubuntu. Alternatively, the user can give up on administrator rights in exchange for better hardware and faster builds, but in this case one must request repositories and packages to be whitelisted by the Travis team [2], [3], [4], which is often inconvenient.

and how you change the .travis.yml file to specify one of those versions ?

For an example of how to set up Travis to test on several versions of GCC and Clang, you can take a look at Metal's '.travis.yml' [5], although there are plenty of other good examples out there, for instance you can also check Boost.Hana and Metabench. [1]: https://github.com/brunocodutra/metal/issues/51 [2]: https://github.com/travis-ci/apt-source-whitelist [3]: https://github.com/travis-ci/apt-package-whitelist/blob/master/ubuntu-trusty [4]: https://github.com/travis-ci/apt-package-whitelist/blob/master/ubuntu-precis... [5]: https://github.com/brunocodutra/metal/blob/master/.travis.yml Regards, Bruno