Skip to content

Normalise feature set of Android build script with other platform builders #146450

Description

@freakboy3742

The Android build script has a couple of minor differences to the iOS and Emscripten build scripts that are relatively easy to accomodate:

  • The build target only allows you to to specify a host, not build or hosts or all
  • The clean target doesn't have allow you to specify a host at all, so you can't delete all host builds without also deleting the build python, or clean a single host (at least, not with the clean command)
  • The cache folder for downloads isn't configurable
  • The cross-build directory isn't configurable.

We should aim for feature parity and consistency of UI between these scripts, wherever possible.

Linked PRs

Activity

  1. self-assigned this
    on Mar 26, 2026
  2. added
    type-featureA feature request or enhancement
    buildThe build process and cross-build
    on Mar 26, 2026
  3. akanil18 commented on Mar 26, 2026

    @akanil18

    Hi @freakboy3742, I would love to work on this issue!

    To achieve feature parity and UI consistency with the iOS and Emscripten build scripts, here is my proposed approach:

    1. build target: Update the argument parsing logic in the Android build script to accept build, hosts, and all as valid targets alongside specific hosts.
    2. clean target: Modify the clean command to accept an optional host argument, allowing users to selectively clean specific host builds, all host builds, or the build python without wiping everything.
    3. Configurable Directories: Introduce CLI flags (and environment variable fallbacks, if applicable) for configuring both the download cache folder and the cross-build directory. I will review the iOS and Emscripten build scripts first to ensure the argument naming conventions exactly match.

    If this approach looks good to you, could you please assign this issue to me? I'll get started on a PR right away.

  4. freakboy3742 commented on Mar 26, 2026

    @freakboy3742
    ContributorAuthor

    @akanil18 The issue is already assigned to me, and there's already an open PR.

    I would also note that this has all the hallmarks of an AI-generated response that is only repeating the information that is in the original ticket. This sort of comment isn't helpful, as it doesn't add anything to the conversation.

  5. added a commit that references this issue on Apr 4, 2026
  6. added 2 commits that reference this issue on Apr 4, 2026
  7. added 2 commits that reference this issue on Apr 4, 2026
  8. added a commit that references this issue on Apr 12, 2026
  9. added 2 commits that reference this issue on Apr 12, 2026
  10. added 2 commits that reference this issue on Apr 13, 2026
  11. added a commit that references this issue on Apr 13, 2026
  12. added 2 commits that reference this issue on Apr 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

OS-androidbuildThe build process and cross-buildtype-featureA feature request or enhancement

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions