package size big

[lyz1005]

The online arm64-v8a library is only 844K after compilation, but it's 1M after recompiling locally. Are there any compilation options that need to be configured?

[vrabaud]

Hi, which flags do you use to build your library?

[lyz1005]

plugins {
id 'com.android.library'
}

android {
namespace 'org.aomedia.avif.android'
compileSdk 31

defaultConfig {
    minSdk 21
    targetSdk 31
    versionCode 1
    versionName "1.0"
    testInstrumentationRunner 'androidx.test.runner.AndroidJUnitRunner'
    
    // 只构建arm64-v8a架构以简化测试
    ndk {
        abiFilters 'arm64-v8a'
    }

    externalNativeBuild {
        cmake {
            // C++编译参数：原有基础+追加4个瘦身项
            cppFlags "-Oz",
                    "-U__STRICT_ANSI__",
                    "-fvisibility=hidden",
                    "-ffunction-sections", "-fdata-sections",
                    "-fno-rtti",
                    "-fno-exceptions",
                    "-fomit-frame-pointer",
                    "-fno-unwind-tables", "-fno-asynchronous-unwind-tables",
                    "-fno-stack-protector",
                    "-fno-ident",
                    "-fno-common",
                    "-fmerge-all-constants",
                    "-fno-plt",
                    "-fno-threadsafe-statics",
                    "-fpic", "-std=c++11",
                    "-DANDROID", "-DQPMAKINGDLL", "-DNDEBUG", "-DAVIF_DEBUG=OFF",
                    "-flto=thin",
                    "-march=armv8-a",
                    "-mtune=cortex-a53",
                    "-mno-outline-atomics",
                    // 追加C++专属+通用瘦身项
                    "-fvisibility-inlines-hidden",
                    "-ffast-math",
                    "-fdelete-null-pointer-checks",
                    "-fno-unroll-loops"

            // C编译参数：原有基础+追加3个瘦身项
            cFlags "-Oz",
                    "-U__STRICT_ANSI__",
                    "-fvisibility=hidden",
                    "-ffunction-sections", "-fdata-sections",
                    "-fno-unwind-tables", "-fno-asynchronous-unwind-tables",
                    "-fomit-frame-pointer",
                    "-fno-stack-protector",
                    "-fno-ident",
                    "-fno-common",
                    "-fmerge-all-constants",
                    "-fno-plt",
                    "-fno-strict-aliasing", "-fno-short-enums",
                    "-fpic", "-std=c11",
                    "-DANDROID", "-DQPMAKINGDLL", "-DNDEBUG", "-DAVIF_DEBUG=OFF",
                    "-flto=thin",
                    "-march=armv8-a",
                    "-mtune=cortex-a53",
                    // 追加C通用瘦身项
                    "-ffast-math",
                    "-fdelete-null-pointer-checks",
                    "-fno-unroll-loops"

            // CMake参数：修复--strip-all+追加2个链接项+2个兜底项
            arguments "-DCMAKE_BUILD_TYPE=MinSizeRel",
                    "-DANDROID_SUPPORT_FLEXIBLE_PAGE_SIZES=ON"
        }
    }


}

buildTypes {
    release {
        minifyEnabled true
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'

        // 启用NDK strip和最大化优化
        packagingOptions {
            doNotStrip '*/mips/*.so'
            doNotStrip '*/mips64/*.so'
        }

        // 更激进的NDK strip配置
        ndk {
            debugSymbolLevel = 'none'
        }
    }
}
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}
externalNativeBuild {
    cmake {
        version '3.22.1'
        path 'src/main/jni/CMakeLists.txt'
    }
}

// 指定使用NDK 23.1.7779620 (clang 12.0.8)
ndkVersion "27.2.12479018"

}

dependencies {
implementation "androidx.annotation:annotation:1.6.0"
androidTestImplementation 'junit:junit:4.+'
androidTestImplementation 'androidx.test.ext:junit:1.1.5'
androidTestImplementation 'com.google.truth:truth:1.1.3'
androidTestImplementation 'androidx.test:runner:1.5.2'
}

[lyz1005]

#!/bin/bash

超级极简 dav1d 静态库构建脚本 - 完全复制工作版本

echo "=== 超级极简 dav1d 静态库构建 ==="

使用指定的 NDK 23.1 版本

ANDROID_NDK="/Users/luyuzhi/Library/Android/sdk/ndk/27.2.12479018"
SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
LIBAVIF_ROOT="$( cd "$SCRIPT_DIR/.." && pwd )"

直接在libavif/ext/dav1d目录下构建

cd "$LIBAVIF_ROOT/ext/dav1d"

如果dav1d目录不存在，先下载

[ ! -f "meson.build" ] && cd "$SCRIPT_DIR" && ./dav1d_download.sh && cd "$LIBAVIF_ROOT/ext/dav1d"

设置工具链

android_bin="$ANDROID_NDK/toolchains/llvm/prebuilt/darwin-x86_64/bin"

架构和工具链映射（完全复制工作版本）

ABI_LIST=("armeabi-v7a" "arm64-v8a" "x86" "x86_64")
ARCH_LIST=("arm" "aarch64" "x86" "x86_64")

#ABI_LIST=("arm64-v8a" )
#ARCH_LIST=( "aarch64")

for i in "${!ABI_LIST[@]}"; do
abi="${ABI_LIST[i]}"
arch="${ARCH_LIST[i]}"

echo "构建 $abi..."
# 架构特定的汇编配置（基于工作版本）

if [ "$abi" = "x86" ] || [ "$abi" = "x86_64" ]; then

if [ "$HAS_NASM" = false ]; then

ASM_OPTION="-Denable_asm=false"

echo " 禁用 $abi 汇编优化（nasm 缺失）"

else

ASM_OPTION="-Denable_asm=true"

echo " 启用 $abi 汇编优化"

fi

else

# ARM 架构默认启用汇编，不需要显式设置

ASM_OPTION=""

echo " 启用 $abi 汇编优化（默认）"

fi

SIZE_OPTIMIZATION="-Denable_asm=false"

# 清理并重新构建 - 完全复制工作版本
rm -rf "build/$abi"
mkdir -p "build/$abi"
cd "build/$abi"

# 设置架构特定的工具链 - 完全复制工作版本
if [ "$abi" = "armeabi-v7a" ]; then
    android_target="armv7a-linux-androideabi21"
    host="arm-linux-androideabi"
elif [ "$abi" = "arm64-v8a" ]; then
    android_target="aarch64-linux-android21"
    host="aarch64-linux-android"
elif [ "$abi" = "x86" ]; then
    android_target="i686-linux-android21"
    host="i686-linux-android"
elif [ "$abi" = "x86_64" ]; then
    android_target="x86_64-linux-android21"
    host="x86_64-linux-android"
fi

android_cc="$android_bin/${android_target}-clang"
android_ar="$android_bin/llvm-ar"

# 创建交叉编译配置文件 - 完全复制工作版本
cat > cross_file.txt << EOF

[binaries]
c = '$android_cc'
cpp = '$android_bin/${android_target}-clang++'
ar = '$android_ar'
strip = '$android_bin/llvm-strip'

[host_machine]
system = 'android'
cpu_family = '$host'
cpu = '$host'
endian = 'little'

[properties]
needs_exe_wrapper = true
EOF

# 完全复制工作版本的meson配置
CC=$android_cc \
AR=$android_ar \
PATH=$PATH:$android_bin \
meson setup \
    --default-library=static \
    --buildtype release \
    --cross-file cross_file.txt \
    $ASM_OPTION \
    -Denable_tools=false \
    -Denable_tests=false \
    -Denable_examples=false \
    -Dlogging=false \
    ../..

# 构建 - 完全复制工作版本
ninja

cd "$LIBAVIF_ROOT/ext/dav1d"

done

echo "构建完成！产物位置: build/*/src/libdav1d.a"

[lyz1005]

一个很奇怪的现象， libdav1d.a v7a 大于v8a

[lyz1005]

一个很奇怪的现象， libdav1d.a v7a 大于v8a

dav1d 1.2.1

[wantehchang]

Vignesh: Could you take a look at this issue? Thanks.

[lyz1005]

我使用了 implementation 'org.aomedia.avif.android:avif:1.0.1.262e11d'， aar 中包含了libavif_android.so =844K，因为要适配16KB，基于 tag 1.0.1 commit 262e11d 进行编译。编译的so 差不多大了100K，目前分析应该是在 dav1d 编译静态.a 时配置不同

[lyz1005]

https://github.com/AOMediaCodec/libavif/blob/main/android_jni/README.md 按照这个方式编译的aar，分析的 libavif_android.so 会比较大

[FooIbar]

Looks like a duplicate of #2884
The maven artifacts are built by internal tools instead of CMake as mentioned in #2464 (comment)

[lyz1005]

Looks like a duplicate of #2884 The maven artifacts are built by internal tools instead of CMake as mentioned in #2464 (comment)

是类似的问题，具体使用了什么策略进行构建呢，或者可以对 1.0.1 提供一个支持16KB的版本吗

[lyz1005]

我发现编译.a 的时候使用 bitdepth 8或者16 会缩小包体，想了解一下你们编译的时候有用过这种配置吗

[vigneshvg]

I used the implementation 'org.aomedia.avif.android:avif:1.0.1.262e11d', and the aar file contains libavif_android.so = 844K. Because I need to adapt to 16KB, I compiled it based on tag 1.0.1 commit 262e11d . The compiled .so file is about 100K larger. My current analysis is that the problem is due to different configurations when compiling the static .a file in dav1d.

Is there any reason why you cannot use the latest version of libavif that's on maven: 1.3.0.841110fd

Or could you provide a version that supports 16KB for version 1.0.1?

sorry 1.0.1 is more than 2 years old now, so we are not planning to update that specific version.

The maven hosted version is generated by google internal toolchain and is likely applying some optimizations that are making the binary smaller. I don't exactly know what the exact difference is between that and the CMake builds.

For your problem though, my recommendation would be to use the latest version from maven which is 1.3.0.841110fd

[lyz1005]

I used the implementation 'org.aomedia.avif.android:avif:1.0.1.262e11d', and the aar file contains libavif_android.so = 844K. Because I need to adapt to 16KB, I compiled it based on tag 1.0.1 commit 262e11d . The compiled .so file is about 100K larger. My current analysis is that the problem is due to different configurations when compiling the static .a file in dav1d.

Is there any reason why you cannot use the latest version of libavif that's on maven: 1.3.0.841110fd

Or could you provide a version that supports 16KB for version 1.0.1?

sorry 1.0.1 is more than 2 years old now, so we are not planning to update that specific version.

The maven hosted version is generated by google internal toolchain and is likely applying some optimizations that are making the binary smaller. I don't exactly know what the exact difference is between that and the CMake builds.

For your problem though, my recommendation would be to use the latest version from maven which is 1.3.0.841110fd

1.有一些定制化需求需要基于1.0.1 开发
2.一直使用1.0.1，变更1.0.3需要灰度验证；
主要是第一点原因，需要自编译。
我的对比是从maven aar 下载 1.0.1.262e11d，解压 libavif_android.so = 844K，自编译 libavif_android.so = 895.26 KB
我的分析maven aar 不至于对 so 的大小进行影响吧
基于 @FooIbar 使用的内部工具编译
我的想法 1. 是否可以基于1.0.1 我单独拆个分支，merge到 libavif，由libavif 帮我构建一下。2.提供一个可对外的构建脚本帮助构建，以上麻烦帮忙看下是否可支持

[vigneshvg]

1. Some customized requirements necessitate development based on version 1.0.1.

Please note that libavif API is generally backwards compatible. So whatever dependency you have should just work with the latest version without needing any changes on your downstream code.

1. Could I create a separate branch based on 1.0.1, merge it into libavif, and let libavif build it for me? 2. Could I provide an externally accessible build script to assist with the build process? Please check if these are supported.

Can you try setting "-Os" in the C/C++ compiler flags to see if that reduces the binary size?

Unfortunately, there is no way to share the build scripts used to build the maven packages externally.