summaryrefslogtreecommitdiff
path: root/other/travis/toxcore-script
AgeCommit message (Collapse)Author
2016-11-06Remove assocendoffile78
2016-11-06Enable address sanitizer on the cmake build.iphydf
2016-10-06Set log level for DEBUG=ON to LOG_DEBUG.iphydf
We use TRACE=ON (cmake flag) to enable LOG_TRACE. This way, a regular build can enable DEBUG while not paying the price of TRACE. This is particularly important for FFI bindings (especially Python), where invoking callbacks can be an expensive operation.
2016-10-05Add option to build tox-bootstrapdMaxim Biro
When cross-compiling to <target> from Linux, cmake might find native Linux libconfig and decide to build tox-bootstrapd. If the target is Windows, this will fail, as tox-bootstrapd can't be built for Windows in the first place. If the target is Linux of some other architecture, then using host native libconfig will fail too. Thus an option is needed to guard against this.
2016-10-04Align things nicerMaxim Biro
2016-10-04Use TEST_TIMEOUT_SECONDS cmake flag on TravisMaxim Biro
2016-09-20Add OSX and Windows build to travis config.iphydf
Tests for Windows are disabled for now, until we figure out which tests can successfully run on wine and select only those.
2016-09-19Add STRICT_ABI cmake flag to generate export lists.iphydf
Enabling this flag will generate and use an LD version script. It ensures that the dynamic libraries (libtoxcore.so, libtoxav.so) only export the symbols that are defined in their public API (tox.h and toxav.h, respectively).
2016-09-16Clean up Travis build a bit in preparation for osx/win.iphydf
2016-09-16Remove format-source from travis script.iphydf
This test is already performed by `make test` later on. We originally had it in the Travis script to make it fail fast when the format is wrong, but there is also some value in running all tests despite format errors. Fixes #83. There are no more relevant phases that would benefit from the padding lines proposed.
2016-09-08Add address sanitizer option to cmake file.iphydf
2016-08-27Move logging to a callback.iphydf
This removes the global logger (which by the way was deleted when the first tox was killed, so other toxes would then stop logging). Various bits of the code now carry a logger or pass it around. It's a bit less transparent now, but now there is no need to have a global logger, and clients can decide what to log and where.
2016-08-24Add cmake test for apidsl.iphydf
2016-08-20Build assoc DHT code on travis.iphydf
2016-08-20Add format-source script.iphydf
This is easier to use from a precommit hook, so it can be used to ensure that all formatting is correct before committing code.
2016-08-17Add missing DHT_bootstrap to CMakeLists.txt.iphydf
- This PR also adds a DEBUG cmake option that enables -DTOX_DEBUG. - We also remove `-Wall`, because there are too many warnings, and nobody really looks at them at the moment. We'll see about fixing them soon. We'll also want to enable `-Werror` at some point. - Finally, this PR enables `-O3` to make sure toxcore still works correctly under heavy compiler optimisations.
2016-08-16Split toxcore into layers.iphydf
This allows us to more clearly define interfaces between modules, and have the linker help us ensure that module boundaries are respected. The onion/tcp/net_crypto layer is a bit too large. This is due to a cyclic dependency (onion -> net_crypto -> TCP -> onion). We may or may not want to break that cycle in the future to allow the onion library to exist on its own without net_crypto.
2016-08-12Add "make install" step to Travis build.iphydf
2016-08-12Add and use CMake build scriptiphydf
Also, fix the hstox build that was taking half an hour. It now takes 5 minutes. Also, perform distcheck on travis to ensure that make dist works. It's not actually failing the build at the moment due to broken tests.
2016-08-12Check code formatting on Travis.iphydf
We run astyle on Travis and check if there is a diff. The build terminates if git finds a difference.
2016-08-12Move toxcore travis build scripts out of .travis.yml.iphydf
This is in preparation for having multiple types of build. One of the future builds will be a hstox build, another may be frama-c or some other static analyser. It makes sense to split these up into multiple builds, because each of them can take a while, and running them in parallel will speed things up. Also, the hstox test coverage should be reported separately from the toxcore auto_test coverage.