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. |
||
|---|---|---|
| .. | ||
| boot_images | ||
| esp-idf-template | ||
| __init__.py | ||
| arduino_cli.py | ||
| asm8080.py | ||
| asmz80.py | ||
| board_access.py | ||
| c_compile.py | ||
| chip_compile.py | ||
| esp32_flash_image.py | ||
| esp32_i2c_slaves.py | ||
| esp32_lib_bridge.py | ||
| esp32_lib_manager.py | ||
| esp32_sd_slave.py | ||
| esp32_signals.py | ||
| esp32_spi_slaves.py | ||
| esp32_worker.py | ||
| esp_qemu_manager.py | ||
| espidf_compiler.py | ||
| gpio_shim.py | ||
| qemu_manager.py | ||
| rom_compile.py | ||
| signal_router.py | ||
| stm32_lib_manager.py | ||
| stm32_worker.py | ||
| wasm_chip_runtime.py | ||
| wasm_chip_slave.py | ||
| wifi_status_parser.py | ||