|
110d17c6
|
2018-06-23T23:17:07
|
|
travis: pin meson to an older version so it works with Python 3.4
The CI image only has Python 3.4. It's a bit of a hassle to change this,
so let's pin meson to the version before they bumped their requirement
instead.
I suppose it's not that bad in that it will guarantee compatibility with
older meson over time.
Signed-off-by: Ran Benita <ran234@gmail.com>
|
|
|
10e1a1b1
|
2017-12-12T14:53:25
|
|
travis: ensure all tests are valgrind-clean
The tests will fail if they have any memory leaks or perform invalid
accesses.
Signed-off-by: Ran Benita <ran234@gmail.com>
|
|
|
86434d84
|
2017-07-25T21:57:42
|
|
build: add meson build system
Meson is easier to maintain, much faster, encourages better practices,
and is not built on a pile of shell scripts.
The autotools build system is kept intact for now, in order to ease the
migration. The intention is to remove it sooner rather than later, if
all goes well.
Run `meson build && mesonconf build` to see the configuration options
for the new system. Conversion should be straightforward. Environment
variables like CFLAGS work the same.
If meson is used, xorg-util-macros is not required.
In terms of functionality the two systems have about the same
capabilities. Here are some differences I noticed:
- Meson uses `-g` by default, autotools uses `-g -O2`.
- In autotools the default behavior is to install both static and shared
versions of the libraries. In meson the user must choose exactly one
(using -Ddefault_library=static/shared).
It is possible to workaround if needed (install twice...), but
hopefully meson will add the option in the future.
- Autotools has builtin ctags/cscope targets, meson doesn't.
Easy to run the tools directly.
- Meson has builtin benchmarks target. Handy.
- Meson has builtin support for sanitizers/clang-analyzer/lto/pgo/
coverage etc. Also handy.
Signed-off-by: Ran Benita <ran234@gmail.com>
|
|
|
a0c858cd
|
2017-07-31T18:22:54
|
|
travis: do the build out-of-tree
To catch problems like the previous commit.
Signed-off-by: Ran Benita <ran234@gmail.com>
|
|
|
ba3e6ce7
|
2016-03-15T19:44:48
|
|
travis: remove --disable-x11
Looks like the CI machines can use Ubuntu 14.04, which has libxcb 1.10,
which is new enough. Lets see if it works.
Signed-off-by: Ran Benita <ran234@gmail.com>
|
|
b04344ff
|
2016-03-15T11:30:57
|
|
travis: Enable documentation build
Make sure Doxygen is installed before we build.
Signed-off-by: Daniel Stone <daniels@collabora.com>
|
|
|
3013633b
|
2014-04-06T16:37:04
|
|
Add .travis.yml file
This CI service https://travis-ci.org/ builds the project in several
configurations, runs the tests, and if something fails it sends an email.
Testing on some other systems is always good, and there don't seem to
be any drawbacks to this, so why not.
Signed-off-by: Ran Benita <ran234@gmail.com>
|