← Back to issue list

Allow build-for "all" for platform-independent builds.

View original Github issue

Metadata

Project
craft-application
Number
#360
Type
issue
State
closed
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

Closed without implementation due to inactivity. The request to support all as a build-for architecture for platform-independent builds was abandoned. No resolution, merge, or follow-up PR was created.

Suggested action:

No scores available.

Issue body

### What needs to get done 1. A `Platform` needs to accept a `build-for` architecture of "all" as the only architecture: https://github.com/canonical/craft-application/blob/11b4fff6c4cbb9dfb78720bb23bb9ddbaa6f614f/craft_application/models/project.py#L103 2. `--build-for` needs to accept `all` as a valid architecture. 3. An application should be able to disable this (e.g. Rockcraft) And tests to ensure that an application works with this in mind. ### Why it needs to get done Older Snapcraft and Charmcraft supported this. https://forum.snapcraft.io/t/architectures/4972/25

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without implementation due to inactivity. The request to support all as a build-for architecture for platform-independent builds was abandoned. No resolution, merge, or follow-up PR was created.
qwen/qwen3.6-35b-a3b Closed without implementation. The request to accept all as a build-for architecture received no code changes or pull requests. The issue was abandoned or deferred without resolution.
qwen3.6-35b-a3b-mtp-q6 Closed without implementation or merged pull request. The feature request to support platform-independent "all" builds was likely abandoned or superseded, as no code changes or tests were added.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1019 Allow platform-independent builds with the "all" architecture craft-parts open Feature request to allow 'all' as a build-for architecture in ProjectInfo for platform-independent builds, with per-plugin checks. Unimplemented; counterpart requests in craft-application and snapcraft were closed without implementation or rejected.
83%
#254 Implement --build-for in addition to --platform craft-application closed Closed without implementation or an associated pull request. No fix or merge details were provided, indicating the feature request was likely abandoned or deferred.
77%
#92 Add a short form for platform `all` debcraft open Feature request to accept a platform named 'all' in debcraft.yaml, meaning build on any architecture and build for the current architecture. No maintainer response, labels, or code changes yet; unimplemented.
73%
#365 feat: accept build-for: [all] in platforms craft-application merged Merged via rebase after approval and passing CI. Enables build-for: [all] in platform definitions, restricting other platforms when used. Resolves #360.
71%
#355 Allow filtering platforms to build-for rockcraft closed Adding a --platform flag for build target filtering was closed without implementation or discussion. The request was abandoned.
71%
#4603 Investigate proper support for "build-for: all" snapcraft closed Support for build-for: all was rejected in core24 due to limited demand for architecture-independent snaps. Alternatives like per-arch builds and remote-build suffice. The feature remains disabled; users should file new tickets for specific use cases.
71%
#4854 Accept `build-for: [all]` and `--build-for=all` for architecture-independent snaps snapcraft closed Closed without resolution. The request to add tests and fix regressions for architecture-independent snaps on core22 and core24 was abandoned with no implementation recorded.
70%