- 27 Dec, 2016 2 commits
-
-
Luca Boccassi authored
Solution: rework the bash test to avoid build failures as intended and make it an easier one-liner
-
Luca Boccassi authored
Solution: use packages on Ubuntu and brews on OSX. The packages and the brews are always kept up to date, so it's no use to rebuild the libsodium stable branch manually everytime.
-
- 09 May, 2016 1 commit
-
-
Kevin Sapper authored
Solution: Use travis to deploy these artifacts automatically. The deployment is triggered by tagging on the zeromq/libzmq repository. Of the many builds travis is checking only the default one with libsodium and drafts disabled is used for deployment. For now the results of `make distcheck` are deployed as well as their md5 and sha1 hash sums. Further changes may upload a generated Changelog as well.
-
- 02 May, 2016 1 commit
-
-
Luca Boccassi authored
Solution: do default test with DRAFT APIs enabled
-
- 06 Mar, 2016 2 commits
-
-
Luca Boccassi authored
Solution: run make dist-check, which will run additional tests, including making sure that the library is installable and the distributable tarball is buildable, along with the usual make and make check.
-
Luca Boccassi authored
Solution: simply run make VERBOSE=1 check instead of manually checking for return value and cat'ing the log file. With VERBOSE, on error the log file will be automatically printed.
-
- 11 Feb, 2016 2 commits
-
-
Luca Boccassi authored
Solution: establish a matrix of CI options. On one axis we have the build system (autotools, cmake, android) and on the other axis we have the encryption options (tweetnacl, libsodium or none).
-
Luca Boccassi authored
Solution: build by default with tweetnacl, and add sub-build project to test libsodium
-
- 04 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: checkout stable branch instead. Several warnings are printed when building from the master branch, and developers recommend using the stable branch instead.
-
- 19 Dec, 2015 1 commit
-
-
Constantin Rack authored
Solution: add `--depth 1` parameter to `git clone` commands
-
- 25 Nov, 2015 1 commit
-
-
Constantin Rack authored
Currently, a test fails on Travis-CI but that can not be reproduced locally. Without the contents of the test-suite.log, this is difficult to analyze. Solution: print test-suite.log if "make check" fails This is based on the following answer on SO: http://stackoverflow.com/a/32597140
-
- 16 Aug, 2015 3 commits
-
-
Luca Boccassi authored
-
Luca Boccassi authored
-
Luca Boccassi authored
-
- 02 Aug, 2015 1 commit
-
-
Luca Boccassi authored
ldconfig is not available on OSX, so Travis CI build fails
-
- 03 Nov, 2014 1 commit
-
-
Joe McIlvain authored
Solution: Add qt-android build system and add to travis-ci
-