On 9/21/24 12:52, Ludovic LANGE via OvmsDev wrote:
I understand that you're trying to setup the toolchain, but I'm wondering it you're doing it the way ESP-IDF "wants" you to ( https:// docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/linux- macos-setup.html#get-started-set-up-tools ).
There is a relationship between ESP-IDF's version, and the toolchain. And during the install of a specific ESP-IDF version it will (locally) install the proper toolchain. (Note: I don't think they deliver a FreeBSD version... and I don't have an Ubuntu box to test. But at least on my macos setup it works like this - and the env variable IDF_TOOLS_PATH points to the toolchain).
You can find the proper versions here : https://github.com/espressif/ esp-idf/blob/master/tools/tools.json (change
masterwith the ESP-IDF version you need) - Only Linux, MacOS, Windows.Maybe you could start with a proper Linux install with the
| install.sh| command, then replicate the version on FreeBSD.
[...]
$ switch-idf 5.2.2 $ xtensa-esp32-elf-cc --version xtensa-esp-elf-cc (crosstool-NG esp-13.2.0_20230928) 13.2.0 Copyright (C) 2023 Free Software Foundation, Inc. $ switch-idf 5.3.0 $ xtensa-esp32-elf-cc --version xtensa-esp-elf-cc (crosstool-NG esp-13.2.0_20240530) 13.2.0 Copyright (C) 2023 Free Software Foundation, Inc.Let me know if it helps.
No, espressif does not provide FreeBSD versions of their toolchains.
And yes, that is helpful; looking at tools/tools.json for 5.3.1 I see it's still using 13.2.0_20240530 so I focus on that version.
Here's some info about what I'm upgrading from:
https://www.freshports.org/devel/xtensa-esp32-elf/It is a lot of work to make this guy build within the FreeBSD ports system, I have to identify and pre-download all of the source blobs prior to the build because ports aren't allowed to use the network during the build... (And it doesn't help that bootstrapping a cross compiler takes a long time.)
Craig