Merge pull request #7 from Javernaut/ci_integration

Ci integration

.travis.yml

@@ -0,0 +1,12 @@
+language: android
+dist: trusty
+before_install:
+  # Installing the ndk and assembling the FFmpeg
+  - yes | sdkmanager "ndk-bundle"
+  - yes | sdkmanager "patcher;v4"
+  - export ANDROID_NDK_HOME=/usr/local/android-sdk/ndk-bundle
+  # Keeping track of the NDK version that was used
+  - cat $ANDROID_NDK_HOME/source.properties
+script:
+  - bash -e ffmpeg-android-maker.sh
+  - cat stats/text-relocations.txt

README.md

@@ -1,5 +1,7 @@
 # ffmpeg-android-maker
 
+[![Build Status](https://travis-ci.org/Javernaut/ffmpeg-android-maker.svg?branch=master)](https://travis-ci.org/Javernaut/ffmpeg-android-maker)
+
 Here is a script that downloads the source code of [FFmpeg](https://www.ffmpeg.org) library and assembles it for Android. The script produces shared libraries as well as header files. The output structure looks like this:  
 <img src="https://github.com/Javernaut/ffmpeg-android-maker/blob/master/images/output_structure.png" width="200">  
 The actual content of all this directories depends on how the FFmpeg was configured before assembling. For my purpose I enabled only *libavcodec*, *libavformat*, *libavutil* and *libswscale*, but you can set your own configuration to make the FFmpeg you need.
@@ -26,4 +28,6 @@ And the actual Android app can be found [here](https://github.com/Javernaut/What
 
 **Setting your own FFmpeg version**. You can actually override the version of FFmpeg used by the script. See details [here](https://github.com/Javernaut/ffmpeg-android-maker/wiki/Invocation-parameters).
 
+**Test your script in a cloud**. This repository has CI integration and you can use it too for your own configurations of FFmpeg. See details [here](https://github.com/Javernaut/ffmpeg-android-maker/wiki/Build-automation).
+
 **Text relocations monitoring**. After a build you can look into stats/text-relocations.txt file. That file lists all *.so files that were built and reports if they have text relocations. If you don't see any mentioning of 'TEXTREL' in the file, you are good. Otherwise, you will see exact binaries that have this problem.