Android: managed toolchain install with license acceptance
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- android, csharp
- Domain
- build-system, devtools
Research direction
Start with the Android plan task C4b, then review dependencies #267 and #254 and the platform roadmap #100; the issue names no implementation files or tests. Map how Android export, InstallAndroidDependencies, the Studio action, and turian toolchain install android fit together. Done means a fresh Linux user without sudo can export for Android after accepting Google's license and installing the pinned toolchains.
Written by the indexing model from the issue text.
Description
Current State
The Android SDK license forbids redistribution, so Turian cannot ship it; system-wide .NET SDKs (/usr/lib/dotnet) cannot install workloads without sudo.
Tasks
- Show Google's license text and require acceptance
-
dotnet workload install android, with a user-local .NET SDK (dotnet-install) when the system SDK is not writable -
InstallAndroidDependenciesinto~/.gaya/toolchains/android/{sdk,jdk}at pinned versions - Studio action and
turian toolchain install android
Acceptance Criteria
- A fresh Linux user without sudo gets a working Android export
Related
- Android plan task C4b · seniority Sr · local-only on
feat/android-platformuntil .NET 11 GA and CI support - Depends on: #267, #254
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:build c:editor p:medium size:XL t:feature
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
c:build p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
c:build c:ui p:low size:L t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
c:assets c:build p:low size:S t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
bug misleading tooling trivial
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Docs example projects pinned to a literal library version instead of 3.*Possibly taken @DaveSkender claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facioquo/stock-indicators-dotnet#2372 ·
Maintainers usually reply within 1 day
-
[Docs] officecli-docx SKILL.md still describes `\n` as a soft line break after #262Possibly taken @giprime claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Facepunch/sbox-public#12097 ·
Maintainers usually reply within 2 days