Esp-idf matter example issue with -import-bridging-header

Vybo · 2024-07-25T11:52:31.738Z

Hello, I've been trying to get the example build a few times on 2 separate machines recently and I always fail during the build with the output ending with "[7/132] Building Swift Module '__idf_main' with 6 sources
FAILED: esp-idf/main/__idf_main.swiftmodule ........... Matter/Node.swift
error: unknown argument: '-import-bridging-header'".

From what I gather, this happens if one were to try using Swift toolchain that does not contain Swift Embeded yet.

However, I'm pretty positive that I have the toolchain set up correctly. My setup:

I use VSCode on macOS 14.5. I have Xcode 15.4 and the latest nightly Swift from main (swift-DEVELOPMENT-SNAPSHOT-2024-07-24-a-osx).

In VSCode, I have installed:

Swift support
ESP-IDF 5.2.2 (tried with 5.3 on a second machine as well)
Installed ESP-Matter successfully
Configured the example workspace for ESP-IDF, ESP-Matter
Configured VSCode to use the Swift nightly toolchain (I also tried the export in terminal). Output of % swift --version
Apple Swift version 6.0-dev (LLVM 3c6e1d334961f5e, Swift 384d7f77a53d8a0)
CMake version is 3.30.1

I can get a normal ESP example to build (some that does not use Swift Embeded).

Any ideas where I might've made a mistake in setting up the environment?

I've tried the terminal approach set up on the second machine as well, but I have the same issue there as well (along with some other Python issues that do not happen on this primary machine).

Setting/resetting the command line tools did not help me as it did the other devs, they were always set properly to the Xcode 15.4 ones (I have tried though).

iQQator · 2024-07-25T14:31:52.363Z

What ESP device is the program written for?
I tried to write under ESP32-C3, but it didn’t work because the Matter in the example only wants ESP32-C6 :)

Vybo · 2024-07-25T14:37:06.573Z

It's the 'smart-light' example in the ' swift-matter-examples' repository. I have set the build target to the C6 variant.

iQQator · 2024-07-25T14:52:07.842Z

Did you try to complete Documentation ?

Vybo · 2024-07-25T15:02:14.534Z

Yes. The first approach was to follow that on the old machine, which did not work. After getting a second machine, I tried to install everything only through VSCode and got the same results, I always end up with the import headers issue.

kubamracek · 2024-07-25T17:05:52.324Z

error: unknown argument: '-import-bridging-header'".

This means the swiftc compiler that's used is too old. Do you have a nightly toolchain from "main" installed? Can we see your export TOOLCHAINS=... command and output of xcrun -f swiftc and swiftc -v?

iQQator · 2024-07-25T17:24:03.608Z

Did you mean Trunk Development (main) snapshots ?

kubamracek · 2024-07-25T17:24:22.625Z

Yes.

iQQator · 2024-07-25T17:30:33.036Z

Versions:

main: 59202407241a
dev 6.0: 600202407241a

Hmm, have other problem today... can't install esp-matter :(
The problem is python 3.12 :)

Vybo · 2024-07-25T18:11:48.370Z

kubamracek:

swiftc -v

@kubamracek
% xcrun -f swiftc
/Applications/Xcode-15.4.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc

% swiftc -v
Apple Swift version 6.0-dev (LLVM 3c6e1d334961f5e, Swift 384d7f77a53d8a0)
Target: arm64-apple-macosx14.0

That is managed by VSCode, I selected the Swift toolchain by using its Swift extension and the "Select toolchain" command. I tried manually setting the toolchain in its terminal as well, with no change.

The older macbook where I tried the terminal setup approach had the toolchain set normally by export TOOLCHAINS= and I had the correct Swift 6.0 version from those Trunk Development (main) snapshots that I've installed (currently swift-DEVELOPMENT-SNAPSHOT-2024-07-24-a-osx downloaded today on the new VSCode machine, 15-07 on the previous terminal set up machine I believe).

@iQQator
I had that same issue with esp-matter on the older macbook where Python 3.12 was installed. I even submitted issue to esp-idf repo, where a fix was provided for using 'pip3' in the setup script instead of 'pip', but that didn't fix it, it just moved the issue with Python elsewhere. I'd try pyenv and set the global version to 3.9.2 if possible. This new fresh macbook does not have the newer homebrew python installed and esp-matter does install correctly.

iQQator · 2024-07-25T18:15:56.469Z

I fix this issue with python3

github.com/project-chip/connectedhomeip

[v1.2] Fix bootstrapping

project-chip:v1.2-branch ← shubhamdp:fix_py_pkg_version

opened 10:24AM - 24 Jul 24 UTC

shubhamdp

+15 -3

- Cherry picking #32945 to fix #31851 - Bump the pyyaml version to `6.0.1` - B…ump the construct version to `2.10.70` <details> <summary>error due to pyyaml</summary> × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [54 lines of output] running egg_info writing lib/PyYAML.egg-info/PKG-INFO writing dependency_links to lib/PyYAML.egg-info/dependency_links.txt writing top-level names to lib/PyYAML.egg-info/top_level.txt </details> <details> <summary> error due to construct </summary> ``` × python setup.py egg_info did not run successfully. │ exit code: 1 ╰─> [10 lines of output] Traceback (most recent call last): File "<string>", line 2, in <module> File "<pip-setuptools-caller>", line 34, in <module> File "/private/var/folders/34/_563kfb57rj_9n2x3qc8ng5r0000gn/T/pip-install-upc5sc58/construct_47c6216bc9774546a3db803fd2414288/setup.py", line 3, in <module> from construct.version import version_string File "/private/var/folders/34/_563kfb57rj_9n2x3qc8ng5r0000gn/T/pip-install-upc5sc58/construct_47c6216bc9774546a3db803fd2414288/construct/__ini t__.py", line 22, in <module> from construct.core import * File "/private/var/folders/34/_563kfb57rj_9n2x3qc8ng5r0000gn/T/pip-install-upc5sc58/construct_47c6216bc9774546a3db803fd2414288/construct/core. py", line 3, in <module> import struct, io, binascii, itertools, collections, pickle, sys, os, tempfile, hashlib, importlib, imp ModuleNotFoundError: No module named 'imp' ``` </details>

github.com/espressif/esp-matter

Failure while running ninja at SDK installation (CON-1270)

opened 07:53PM - 20 Jul 24 UTC

Mr-Alirezaa

**Describe the bug** I have cloned esp-matter sdk with the following command an…d I'm sure that nothing went wrong during the cloning process: ``` git clone \ --branch release/v1.2 \ --depth 1 \ --shallow-submodules \ --recursive https://github.com/espressif/esp-matter.git ``` After that I tried to install the sdk with `./install.sh` and it failed with the following log. I can also confirm that I have the prerequisites installed as per [this document](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/linux-macos-setup.html#for-macos-users) [esp-matter-installation.log](https://github.com/user-attachments/files/16322155/esp-matter-installation.log) last few lines of the above log: ``` ... File "/Users/a.asadi/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 573, in setup result = step(spin) ^^^^^^^^^^ File "/Users/a.asadi/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 762, in virtualenv if not virtualenv_setup.install( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/a.asadi/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/virtualenv_setup/install.py", line 443, in install install_packages(gn_target) File "/Users/a.asadi/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/virtualenv_setup/install.py", line 424, in install_packages raise subprocess.CalledProcessError( subprocess.CalledProcessError: Command '['ninja', '-C', '/Users/a.asadi/esp/esp-matter/connectedhomeip/connectedhomeip/.environment/gn_out', '-v', ':python_packages.install']' returned non-zero exit status 1. ``` **Environment** - ESP-Matter Commit Id: d692395263fe6cd254b262366635d6b7e6cdad0c (release/v1.2) - ESP-IDF Commit Id: a322e6bdad4b6675d4597fb2722eea2851ba88cb (v5.1.2) - SoC (eg: ESP32 or ESP32-C3): N/A - Device Logs (Please attach the log file): - Host Machine OS: MacOS Sonoma 14.5 (23F79) - Commissioner app and versions if present: - Commissioner's logs if present: **Any additional details** I started by using this https://apple.github.io/swift-matter-examples/tutorials/swiftmatterexamples/setup-macos to setup idf tools and matter sdk on my mac machine to start programming my ESP32C6 with Swift. I have also tried the installation process as the official document said: https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html#esp-matter-setup There are also similar issues I have found in the current repo.

And now try to build project smart-light )

idf.py set-target eps32c3 # in my case
idf.py build

build complete success

But:

i have UTM VM with Sequoia & Xcode 16 (for tests purpose)
i have main Toolchain
i install esp-matter by instructions from github issue :)
i suppress errors in python 3 install by ~/.pip/pip.conf edit with:

[install] 
break-system-package = true

and use micro-app for zsh to run environment for build:

do_esp() {
     export TOOLCHAINS=org.swift.59202407241a
     . ~/esp/esp-idf/export.sh
     . ~/esp/esp-matter/export.sh
}

rhx · 2024-07-26T07:21:10.456Z

If you are building for the ESP32c3 (instead of the c6), you need to add the following lines to the target_compile_options in CMakeLists.txt:

        -Xcc -march=rv32imc_zicsr_zifencei
        -Xcc -mabi=ilp32

Otherwise your binary will likely crash.

Vybo · 2024-07-26T12:23:02.665Z

I got a little bit further today when having Xcode 16 installed (on Sonoma) and using the main Swift toolchain as required by the Documentation. I can't get the example to build, however at least I don't have the issue with the bridging header argument now.

The new error seems to be an issue of the esp-matter library directly. Log here.

iQQator · 2024-07-26T17:47:56.192Z

Yeah, crash on device without this :)

iQQator · 2024-07-26T17:55:54.170Z

rhx:

-Xcc -march=rv32imc_zicsr_zifencei

Where is this options should be ?

rhx · 2024-07-26T20:02:33.272Z

The relevant CMakeLists.txt file is typically in the main folder of the example. E.g., in the led-blink example (under Apple's swift-matter-examples), there is a CMakeLists.txt in the main folder that has the following (line 25 onwards):

# Swift compiler flags to build in Embedded Swift mode, optimize for size, choose the right ISA, ABI, C++ language standard, etc.
target_compile_options(${COMPONENT_LIB} PUBLIC "$<$<COMPILE_LANGUAGE:Swift>:SHELL:
        -target riscv32-none-none-eabi
        -Xfrontend -function-sections -enable-experimental-feature Embedded -wmo -parse-as-library -Osize
        -color-diagnostics
        -Xcc -DCHIP_HAVE_CONFIG_H
        -Xcc -std=c++17
        -cxx-interoperability-mode=default
        -Xcc -fno-exceptions
        -Xcc -fno-rtti

This is where you would insert the two additional options, i.e. add:

        -Xcc -march=rv32imc_zicsr_zifencei
        -Xcc -mabi=ilp32

iQQator · 2024-07-27T09:23:51.358Z

Thanks. I found some information too (patch for project)

github.com/apple/swift-matter-examples

Add `Xcc` flags that fixes crash on ESP32-C3.

apple:main ← cheif:fix/esp32-3c

opened 07:43PM - 10 Jul 24 UTC

cheif

+15 -0

This fixes #15, making the `smart-light` example run on ESP32-C3. I'm don't hav…e enough knowledge to know if this is the proper fix/correct location to add these flags, but it makes the example work for me at least.

iQQator · 2024-07-27T09:26:17.115Z

I suppose this is because swift-6.0 branch doesn't support yet swift embedding, try to use main branch for Toolchains and select toolchains for xcode ;)

Vybo · 2024-07-27T09:33:31.170Z

I have installed the toolchain from 'main' that is linked in the documentation, for example this one. Those are nightly snapshots that now contain Swift 6. I also tried 'Swift 6.0 Development' before which caused the exact same issue.

Maybe you stumbled upon a particular link that contained the correct version or during the time of writing the docs, the nightlies contained a different version? That doesn't make much sense though.

Would you please share your 'swift --version' or 'swiftc -v' output when you have your terminal/environment set for building the example and the build passes?

iQQator · 2024-07-31T10:25:40.861Z

Hi @Vybo

Function for set environment, commented value was develop swift-6.0 branch
Снимок экрана 2024-07-31 в 13.23.53

Versions of swift --version and swiftc -v
Снимок экрана 2024-07-31 в 13.24.47