| Age | Commit message (Collapse) | Author |
|---|
|
|
|
https://www.freebsd.org/cgi/man.cgi?alloca
If stdlib.h does not define alloca, and we're using GCC (or Clang), we
define the macro ourselves in terms of a GCC builtin.
|
|
It's a maintenance burden nobody uses. Let's make toxic the official
console client, instead.
|
|
This basically means: try until you run out of time (50 minutes on
Travis). On Linux, we really want the tests to pass, so there is no point
in limiting the number of retries. On windows, we don't retry, on FreeBSD
it's limited to 1.
|
|
Also replace &(x) with &x for consistency.
|
|
But enable it on circle ci, so at least we have one asan build.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead of updating it in every Travis build.
|
|
|
|
|
|
We can run the spectest from within cmake, so we should exercise that.
|
|
The new encoding is `0` for `Nothing` and `[1, x]` for `Just x`.
|
|
|
|
Fixes #411.
|
|
|
|
|
|
|
|
|
|
tar -jxf expects a file.
|
|
Fixes #363.
|
|
This way we can at least see what fails in which way.
|
|
This one is not allowed to fail and ensures that toxcore can at least be
built for OSX.
|
|
This takes a few seconds but allows us to cover cases that aren't checked
often.
|
|
|
|
We also never really tested this, because we run make distcheck, which
does another configure with default flags instead of the ones we passed.
Fixes #317.
|
|
Build it on Travis. It won't be built on the windows builds regardless
of having it enabled globally.
Fixes #292.
|
|
Having -Werror set by default causes users' builds to fail because
toxcore is not warning-free. Failing on errors is appropriate for the
development phase, e.g. when building it in a CI enviroment, but it
doesn't make much sense to fail builds for users and let them figure out
that they need to pass -DWARNINGS=OFF to make the library build.
|
|
Travis seems to no longer set $TERM, which breaks opam. We now manually
set it to some hopefully sane value.
|
|
|
|
|
|
Compiling as C++ changes nothing semantically, but ensures that we don't
break C++ compatibility while also retaining C compatibility.
C++ compatibility is useful for tooling and additional diagnostics and
analyses.
|
|
This ensures that on Travis, format_test will always be executed, or the
build fails.
|
|
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.
|
|
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.
|
|
|
|
|
|
We'll maintain it in the c-toxcore repo, where it belongs.
|
|
Tests for Windows are disabled for now, until we figure out which tests
can successfully run on wine and select only those.
|
|
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).
|
|
|
|
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.
|
|
This is the first step towards unifying travis configs for toxcore,
hstox, and qtox.
|
|
|
