Replies: 2 comments
|
+1 |
|
The "dependency hell" almost always comes from two things: the pinned Flutter version, and trying to compile the native core yourself. You don't need to compile it — the Go core ( # 1. Use the EXACT Flutter version the repo pins — check `environment: flutter:` in pubspec.yaml.
# A mismatched Flutter SDK is the #1 cause of the conflicts you're hitting. fvm makes this painless.
dart pub global activate fastforge
# 2. Pull Dart deps, run codegen, and fetch the prebuilt native core in one step:
make android-prepare
# -> flutter pub get -> build_runner codegen -> slang translations
# -> downloads hiddify-lib-android.tar.gz into android/app/libs
# 3. Build the APK:
make android-apk-release
# or, for a quick local build: flutter build apk --dart-define sentry_dsn=The step people usually skip is the If you'd rather not fight the local toolchain at all: fork the repo and let the GitHub Actions release workflow build every platform with the exact pinned toolchains. That's how the official releases are produced, and the license requires the fork anyway. |
Uh oh!
There was an error while loading. Please reload this page.
Hi guys, before asking the question, I have read the community contribution and the streamlined build guide, but there are actually a lot of tricky issues (various dependency conflicts), flutter and traditional kotlin projects seem a bit different, has anyone succeeded, I will try as many possibilities as possible without disturbing you, thank you
All reactions