ESP-IDF compike error that git is not finding a repository at /

[LocalNic]

Hi,
ESPHOME is creating problems in the newest / recommended ESP-IDF therefore I suggest to be more specific in the esp: section and define

esp32:
framework:
type: esp-idf
version: 4.4.8
platform_version: 5.4.0

instead of just

esp32:
framework:
type: esp-idf
version: recommended

and update it when the compiler issues have been solved.

compiler issues are a bit missleading that there is no git found at /

[formatBCE]

Thanks for reporting. Will apply today!

[formatBCE]

What actually are the problems you're mentioned?

I just tried to build firmware from scratch, using latest YAML and ESPHome, and everything built successfully.

[LocalNic]

I have a grown HASSOS and run ESPHOME since a few years.
With the update of ESP-IDF to 5.x.y it happens that some sources have problem compiling.

This is the error that you get.
`Reading CMake configuration...
-- Found Git: /usr/bin/git (found version "2.39.5")
-- git rev-parse returned 'fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).'
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /data/cache/platformio/packages/toolchain-xtensa-esp32s3/bin/xtensa-esp32s3-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32s3/bin/xtensa-esp32s3-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /data/cache/platformio/packages/toolchain-xtensa-esp32s3/bin/xtensa-esp32s3-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32s3
NOTICE: Current idf-component-manager default lock file version is 2.0.0, but found 1.0.0 in /data/build/koala-satellite/dependencies.lock. Recreating lock file with the current version.
Manifest files have changed, solving dependencies.
....NOTICE: Updating lock file at /data/build/koala-satellite/dependencies.lock
Processing 2 dependencies:
[1/2] espressif/esp-nn (1.1.0)
[2/2] idf (5.1.5)
-- Configuring incomplete, errors occurred!
See also "/data/build/koala-satellite/.pioenvs/koala-satellite/CMakeFiles/CMakeOutput.log".

fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CMake Error at /data/cache/platformio/packages/framework-espidf@src-6e6cd5244a43bdfe453daac50cfe73b6/tools/cmake/build.cmake:266 (message):
Failed to resolve component 'freertos'.
Call Stack (most recent call first):
/data/cache/platformio/packages/framework-espidf@src-6e6cd5244a43bdfe453daac50cfe73b6/tools/cmake/build.cmake:302 (__build_resolve_and_add_req)
/data/cache/platformio/packages/framework-espidf@src-6e6cd5244a43bdfe453daac50cfe73b6/tools/cmake/build.cmake:303 (__build_expand_requirements)
/data/cache/platformio/packages/framework-espidf@src-6e6cd5244a43bdfe453daac50cfe73b6/tools/cmake/build.cmake:303 (__build_expand_requirements)
/data/cache/platformio/packages/framework-espidf@src-6e6cd5244a43bdfe453daac50cfe73b6/tools/cmake/build.cmake:603 (__build_expand_requirements)
/data/cache/platformio/packages/framework-espidf@src-6e6cd5244a43bdfe453daac50cfe73b6/tools/cmake/project.cmake:604 (idf_build_process)
CMakeLists.txt:3 (project)

========================= [FAILED] Took 18.06 seconds =========================`

If you use a strict definition of the Environment then it will compile.
This is actually a known Problem for all that uses ESP-IDF and not arduino as a framework.

I also know that it is not optimal because the ESP-IDF 5.x.y holds alot of performance improvements.

BTW.: A reinstall of the ESPHOME plugin in HASS don't solve the problem, also cleaning the build won't help.
Maybe it is also just related to the Environment. but for now this is what solves the Problem and till now I cannot see any Problems with the code.

[formatBCE]

Alright. I'll leave this open for information purposes. Won't change main YAML though - it must be local fix for those with such trouble.