e876fbef7f
Two failure modes seen on a fresh docker deploy where the final image's system python differs from the one the IDF venv was created with: - IDF's cmake derives the venv dir name from the SYSTEM python version and fails with 'python doesn't exist' before configure; and when cmake is invoked directly (not via idf.py) its PYTHON property falls back to the bare 'python' from PATH. The Linux branch of _build_env now pins IDF_PYTHON_ENV_PATH to the newest env under the tools root and puts its bin first on PATH (mirroring what the Windows branch already did). - When several toolchain generations share one tools root, glob order decided which won the PATH race. Toolchain dirs are now ordered by the versions the IDF tree declares in tools/tools.json. |
||
|---|---|---|
| .. | ||
| api | ||
| core | ||
| database | ||
| mcp | ||
| models | ||
| schemas | ||
| services | ||
| utils | ||
| __init__.py | ||
| main.py | ||