6 Commits

Author	SHA1	Message	Date
wm4	950ad5a412	README: add a link to the wiki about the FFmpeg vs. Libav issue	2013-10-25 21:23:22 +02:00
Stefano Pigozzi	61790c98e8	README: add clarification about --enable	2013-09-14 10:00:59 +02:00
Stefano Pigozzi	438f9e585d	README: update Contact info with Mailing Lists	2013-09-14 10:00:59 +02:00
wm4	a0f7fa4ac5	README: copy paragraph about --enable-* from configure ... This issue hits users way too often. Copy the explanation printed by the configure script to the README to give it more visibility. We will fix this properly once we have a new build system.	2013-07-16 00:03:51 +02:00
wm4	853b468023	README: small addition to encoding dependencies	2013-07-15 21:43:14 +02:00
Stefano Pigozzi	d8c06cd99e	add Travis-CI integration ... Travis-CI [1] is a continous integration cloud service. It is free for open-source projects and tigthly integrated tiwh GitHub so there is really no reason for us not use it. :) For now we are going to do a total of 4 builds, mainly to test ffmpeg/libav API breakage: * ffmpeg-stable, libass-stable * ffmpeg-git, libass-stable * libav-stable, libass-stable * libav-git, libass-stable The compiler that is currently used is clang for two reasons: * running 8 build targets would be quite wasteful and take a long time * clang is less tested and used during development than gcc (especially on linux) Currently Travis doesn't support OS X environments alongside Linux ones [2]. When it will, we will add a fifth build target to test OS X compilation breakage. README was moved to markdown to add the little build status image. I ran some tests with my GitHub fork and couldn't get images to show up using ReStructured Text. [1]: https://github.com/travis-ci/travis-ci [2]: travis-ci/travis-ci#216	2013-05-19 20:41:40 +02:00