k
/
ffmpeg-android-build
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improving the image displaying in README.md

Browse Source
ffmpeg_4.4.2
Javernaut 6 years ago
parent 888bad910b
commit a9d3cb5ca3
1 changed files with 4 additions and 4 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 8
      README.md

8
README.md
Unescape View File

@ -1,7 +1,7 @@
# ffmpeg-android-maker # ffmpeg-android-maker
Here is a script that downloads the source code of FFmpeg library and assembles it for Android. The script produces shared libraries as well as header files. The output structure looks like this: Here is a script that downloads the source code of FFmpeg library and assembles it for Android. The script produces shared libraries as well as header files. The output structure looks like this:
![Markdown Here logo](images/output_structure.png) ![Markdown Here logo](images/output_structure.png =250x)
The actual content of all this directories depends on how the FFmpeg was configured before assembling. For my purpose I enabled only *libavcodec*, *libavformat* and *libavutil*, but you can set your own configuration to make the FFmpeg you need. The actual content of all this directories depends on how the FFmpeg was configured before assembling. For my purpose I enabled only *libavcodec*, *libavformat* and *libavutil*, but you can set your own configuration to make the FFmpeg you need.
The version of FFmpeg here is **4.1.1**. And the script expects to use Android NDK **r19**. Starting with this versions of FFmpeg and NDK the whole process became much simpler. The version of FFmpeg here is **4.1.1**. And the script expects to use Android NDK **r19**. Starting with this versions of FFmpeg and NDK the whole process became much simpler.
@ -22,8 +22,8 @@ Well, just execute the script :) Examine the `output` directory after.
## Known issues: ## Known issues:
The x86 binary doesn't have assembler optimizations, since they bring text relocations. So it may encounter certain performance issues. The x86_64 doesn't have this problem though. The x86 binary doesn't have assembler optimizations, since they bring text relocations. So it may encounter certain performance issues. The x86_64 doesn't have this problem though.
## TODO: ## TODO:
Upload the sample project where the compiled library is actually used. Upload the sample project where the compiled library is actually used.

Write Preview
Loading…
Cancel
Save