From a9d3cb5ca3c3ca3eecc35201e3a400717e7e49d1 Mon Sep 17 00:00:00 2001 From: Javernaut Date: Sun, 10 Mar 2019 16:06:37 +0100 Subject: [PATCH] Improving the image displaying in README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 68e3ecd..57d394d 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # 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: -![Markdown Here logo](images/output_structure.png) +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 =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 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: -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: -Upload the sample project where the compiled library is actually used. \ No newline at end of file +Upload the sample project where the compiled library is actually used.