Flutter projects tend to use a terrible amount of disk space during their build. Mine runs out of disk space on the CI build server.
Is there a way to increase it?
Thanks
Flutter projects tend to use a terrible amount of disk space during their build. Mine runs out of disk space on the CI build server.
Is there a way to increase it?
Thanks
Yes and no, same for react-native ones.
Which MergeRequest is this about?
There is no MergeRequest yet, I am using the CI from my fork.
How much disk space does the VM have?
Dunno exactly
Can you set Flutter as submodule instead? Encourage devs to switch from srclibs to submodules as much as possible (#2803) · Issues · F-Droid / Data · GitLab
Metadata pls? Fastlane file structure ($1895688) · Snippets · Snippets · GitLab
Why add rust target x86_64 if you don’t build it?
What are zcash parms that you download?
/LE: why rm -fr those at the end?
Do run - flutter config --no-analytic
before config.sh
This builds fine locally
- versionName: 1.2.17
versionCode: 347
commit: b78fb62449fce0ace87e4540ce6a31054e4ca739
submodules: true
sudo:
- apt-get update
- apt-get install cmake build-essential
init:
- mkdir -p $HOME/.zcash-params
- curl https://download.z.cash/downloads/sapling-output.params --output $HOME/.zcash-params/sapling-output.params
- curl https://download.z.cash/downloads/sapling-spend.params --output $HOME/.zcash-params/sapling-spend.params
output: build/app/outputs/flutter-apk/app-release.apk
srclibs:
- flutter@3.3.10
- rustup@1.25.1
prebuild:
- $$rustup$$/rustup-init.sh -y
- source $HOME/.cargo/env
- rustup target add aarch64-linux-android armv7-linux-androideabi
- cargo install --force cargo-ndk duckscript_cli
- export PATH=$$flutter$$/bin:$PATH
- flutter config --no-analytics
- ./configure.sh
- PROJECT_ROOT=$PWD duck misc/fdroid/setup_crate_type.ds
build:
- source $HOME/.cargo/env
- export PATH=$PATH:$$flutter$$/bin
- export JKS_PASSWORD=dummy
- cargo ndk --target arm64-v8a build --release --features=dart_ffi
- mkdir -p ./packages/warp_api_ffi/android/src/main/jniLibs/arm64-v8a
- cp ./target/aarch64-linux-android/release/libwarp_api_ffi.so ./packages/warp_api_ffi/android/src/main/jniLibs/arm64-v8a/
- rm -rf target/aarch64-linux-android
- cargo ndk --target armeabi-v7a build --release --features=dart_ffi
- mkdir -p ./packages/warp_api_ffi/android/src/main/jniLibs/armeabi-v7a
- cp ./target/armv7-linux-androideabi/release/libwarp_api_ffi.so ./packages/warp_api_ffi/android/src/main/jniLibs/armeabi-v7a/
- flutter build apk
ndk: r25b
APK report here: via Virus Total
Your APKs have x86_64 so I guess you’ll bring that back too, right?
Your APKs have “play” stuff inside, you need those? I’m thinking about reproducible builds…
Since it connects to all those sites add on top:
AntiFeatures:
- NonFreeNet
Where do you see the “play” stuff in the report
?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.