Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Build the bundled flatc only when its inputs changed, and build it in parallel

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cmake, python
Área
build-system

Línea de trabajo

Start in hatch_build.py, at _build_flatc(), which currently deletes deps/flatbuffers/build, reconfigures with cmake, and builds flatc on one core. Read the just recipes that invoke the build, and the linked zlmdb issue for the shared design. Done means a stamp stored beside the packaged binary lets an unchanged build be skipped, the build runs with parallel jobs, AUTOBAHN_FORCE_FLATC_BUILD=1 forces a rebuild, and just clean clears the stamp. The issue asks for one implementation synced to zlmdb, so the design needs maintainer agreement first.

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

Descripción

Same problem and same fix as crossbario/zlmdb#TODO. The two repositories share
hatch_build.py _build_flatc().

On every build, including every editable install, _build_flatc() deletes
deps/flatbuffers/build, configures with cmake again, and builds flatc on one core
(cmake --build without --parallel). Local just recipes that install first therefore
rebuild the same flatc from the same source again and again.

Proposal, as detailed in the zlmdb issue:

  • a sha256 stamp over what flatc is built from: the deps/flatbuffers commit (and
    whether it has local changes), the configure arguments, the target platform and
    toolchain, and a version for the build logic. Store it next to the packaged binary;
  • skip the build when the binary exists and the stamp matches. Otherwise build
    incrementally, keeping the build directory unless the configure arguments or the
    toolchain changed;
  • build in parallel (--parallel <os.cpu_count()>, unless CMAKE_BUILD_PARALLEL_LEVEL
    is set);
  • force a rebuild with AUTOBAHN_FORCE_FLATC_BUILD=1, and in just clean.

The toolchain in the stamp also keeps a host-built flatc out of wheels built for
another architecture or libc in a container with the repository mounted.

Both repositories should use the same implementation, so it is written once and then
synced.

Note: This issue was drafted with AI assistance (Claude Code).

Lenguaje dominante
Python
Estrellas
2.5k
Forks
769
Merge medio
1 d 11 h
PR fusionados (30 d)
16

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 crossbario/autobahn-python

Todos los issues de crossbario/autobahn-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.