Native ARM64 Windows build

Abierto
  • ¿Algo no está bien?
#9 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, rust
Área
build-system, ci-cd

Línea de trabajo

Start with the arm64-build branch and .github/workflows/ci.yml, especially the build-arm64 job; the payload reports that this work is already implemented there and not merged. Review the native release build and library test steps, then check the stated gap: the tests/ integration suite has not run on Arm64 because it needs Git Bash paths and an interactive desktop session. Done means that suite runs on Arm64 and its results support the platform claims.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

platform roadmap

Summary

The programs now build natively for aarch64-pc-windows-msvc in continuous integration, and the library unit tests run natively on Windows 11 Arm64. The change is on the arm64-build branch. It is not merged.

The job

build-arm64 in .github/workflows/ci.yml runs on the windows-11-arm hosted runner (image windows-11-vs2026-arm64). It installs the aarch64-pc-windows-msvc target, runs cargo build --release --locked --all-targets for that target, runs cargo test --release --locked --lib natively, and uploads the four programs as the artifact process-tree-guard-aarch64-pc-windows-msvc.

Evidence

Run: https://github.com/WikdSolvemProbler/process-tree-guard/actions/runs/41952589923

  • The release build passed.
  • The library unit tests ran natively on Arm64: 264 passed, 0 failed.
  • All four programs in the artifact carry the ARM64 machine type (0xAA64) in their PE headers.

SHA-256 of the artifact files:

Program SHA-256
process-tree-guard.exe 8c7e66a938f110169fdb6ac32f03976f8b908db1c69f16d65a73c0353243e952
process-tree-guard-contain.exe 427a72d79869def90d0df19cc2172d8b6c2945be3d6cff6f0e27ca3df0419f7b
process-tree-guard-deadline.exe eed79e0e0e5d3de01a6bfba06631b87be3abd26d0aafb9dae73dcb0112770dda
process-tree-guard-gate.exe 7a617ec63e79c299f7b4fc449ab9c9016fac09f7f49c84d0f8f268ab92f21839

Also on the branch

  • install.ps1 prefers the aarch64 zip on Windows on Arm64 when the release has one, with the same SHA256SUMS checks, and otherwise falls back to the x86-64 zip under emulation. It prints which build it chose.
  • wiki/Platform-Support.md states the evidence above in the aarch64 row. The target remains a non-release target.

Not yet covered

  • The integration suite (tests/) has not run on Arm64. It needs Git Bash paths and an interactive desktop session, which a hosted runner does not provide.
  • No release zip for aarch64 exists. A release needs the zip named process-tree-guard-<version>-aarch64-pc-windows-msvc.zip and its entry in SHA256SUMS before the installer will pick it.
  • Until the integration suite runs on Arm64, the programs stand at the type-and-borrow tier for the claims that suite covers.
Lenguaje dominante
Rust
Estrellas
0
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de WikdSolvemProbler/process-tree-guard

Todos los issues de WikdSolvemProbler/process-tree-guard

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.