Reconfigure travis to perform parallel builds and linting #364
Conversation
|
Would it be possible to continue using g++ 4.9 plus the corresponding libstdc++? The versions in the suggested new build configuration unfortunately do not support some C++11 STL functions for example that can be useful. |
|
It would be possible, but a bit more cumbersome, because Ubuntu introduced some bug in 4.9 that makes the corresponding libstdc++ incompatible with clang. The workaround is to make clang compile with -stdlib=libc++ as additional CXXFLAGS. Perfectly doable, but the travis config becomes more messy. Yet if there is a need for doing so then we can certainly go that road. @danpoe Would you say that's preferable? |
|
Are you referring to the |
|
Yes, the max_align_t issue. What I'd like to maintain is parallel runs of the various tasks. I'll try to cook up some best-of version to get us all these features. |
tautschnig
force-pushed
the
travis-reconfig
branch
2 times, most recently
from
517eaf0 to
61eff63
Compare
tautschnig
changed the title
tautschnig
force-pushed
the
travis-reconfig
branch
4 times, most recently
from
3d01951 to
bfc81d0
Compare
The build matrix is constructed from os and compiler. OSX and Linux are picked as operating systems for compilation, and linting is run as a parallel task. Linux uses GCC/g++ 5 and Clang 3.7.
G++-5 warned: "suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’"
tautschnig
force-pushed
the
travis-reconfig
branch
from
bfc81d0 to
0cf0972
Compare
|
I intend to merge the travis configuration fix and 0cf0972 to make miniBDD build using GCC 5. Thus we should be back at a stage were we can reasonably use travis. |
Preparation to use of the reachability slicer before the full-slicer.
The build matrix is constructed from os and compiler.
This should re-enable linting as a parallel, separate task.