Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows user’s choice of compiler to be passed through to build
script for C and C++ without undergoing any processing, as it does now
with C++ (e.g. stripping of version number)
The main reason for this is to avoid duplicating the compiler in the "env" and "compiler"
directives, as here for example:
https://github.com/sfegan/calin/blob/master/.travis.yml
Which would make specifying the build matrix much easier, e.g. as here:
https://github.com/sfegan/travis_container_test/blob/master/.travis.yml
In that last script I would of course have to put some logic in to use the TRAVIS_COMPILER variable to set CC and CPP, but I didn't do that there.
Of course it is possible to avoid the duplication by simply specifying "g++" generically as the "compiler" and using an "env" to specify the version, but that misses out having a per-"compiler" cache (which is essential to me) and also means the true compiler version doesn't show up in the build status page, as here:
https://travis-ci.org/sfegan/travis_container_test
Thanks,
Steve
PS. I love Travis CI