-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build step for 'chip_gn' failed No such file or directory (CON-1419) #1157
Comments
I have the same problem here with esp-matter and swift-matter-examples, Thanks! Let's wait for a fix. |
@North3rnL1ght thanks for the detailed debugging, will see how this can be fixed. On my mac, I am unable to reproduce this. I only see one path in
|
@shubhamdp I found this extra path inside the list of component path output on set-target for esp32c6. Copied only some until the components/chip folder path occours!
The only different version is in cmake:
|
Describe the bug
I downloaded and installed ESP-IDF and ESP-Matter for apple/swift-matter-examples. I used the installation tutorial they provided. But for some reason I can't build the example for the smart-light. I even tried the examples provided inside the esp-matter folder but I always recive the following error during Build.
Environment
ESP-Matter Commit Id: 7b9d69a (grafted, HEAD -> release/v1.2, origin/release/v1.2)
ESP-IDF Commit Id: a322e6bdad4b6675d4597fb2722eea2851ba88cb (grafted, HEAD, tag: v5.2.1)
SoC (eg: ESP32 or ESP32-C3): ESP32-C6
Host Machine OS: MacOS 15.1 (24B83)
Host Machine Python version: 3.9.6
Any additional details
The Problem is that the build.ninja trys to execute the following command:
Which results in "No such file or directory". When I manually edit the build.ninja file and remove the first PATH "/Users/account/esp-matter/connectedhomeip/connectedhomeip/config/esp32/components/chip;" the build executes successfully. I don't know where it takes the first path from. Even tried reinstalling esp-matter and esp-idf but it didn't made any changes.
The text was updated successfully, but these errors were encountered: