mozilla/DeepSpeech

Cross-compilation should document Python host version

Open

#3,635 opened on Apr 21, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C++ (26,755 stars) (4,093 forks)batch import
documentationgood first bughelp wanted

Description

When cross-compiling python binding, we rely on a multistrap generated chroot to build but we still need python on the host as well. Documentation should emphasize that in chroot and host version needs to match (up to major version), e.g., you need 3.7.x for building for a chroot 3.7.y, you can't have chroot using 3.7.y and host being 3.8.z.

Contributor guide

Tech stack
pythoncpp
Domain
documentationbuild system
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with cross compilation conceptsBasic Python version management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Review the existing build documentation for cross compilation, likely in the repository's docs or README. Identify where Python and chroot setup is described. Add a clear note that the host Python version must match the chroot's Python major version (e.g., if chroot uses Python 3.7, host must also use Python 3.7). Ensure the wording is unambiguous to avoid version mismatch issues.