'tox testenv' seems to build and run the test suite.
There does seem to be a few warnings during the build about
meliae/_scanner_core.c:63:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes]
but it does build, and it does pass the test suite.
Would it make sense to update "make check" to use tox internally instead of doing it itself?
'tox testenv' seems to build and run the test suite. _scanner_ core.c: 63:1: warning: function declaration isn’t a prototype [-Wstrict- prototypes]
There does seem to be a few warnings during the build about
meliae/
but it does build, and it does pass the test suite.
Would it make sense to update "make check" to use tox internally instead of doing it itself?