Closed eliandoran closed 1 year ago
We can't run install.sh
in the Nix build environment if it has to download from the network. If the warnings don't stop you from building projects, then I'm not too worried. We might want to figure out if there's a file we can modify to tell ESP-IDF where these tools are when they are installed by Nix, but even then the shell environments for each different ESP32 variant don't install all those tools at the same time.
Something this points out though is that the ULP co-processor toolchains are not explicitly packaged - I'm not sure they come with the toolchains for the ESP32 variants that have the ULP co-processor.
install.sh
so I'm not sure if that changes things.It does point out though that I do need to at least update OpenOCD to the recommended version for ESP-IDF v5.0.2, so I will at least do that, and I'll see if I can get the ULP toolchains too.
tools.json
file in the ESP-IDF checkout - I didn't quite set up all of them, but it should be easy to add ones that aren't currently downloaded and installed. I still don't get the errors/warnings, so I'm going to close this - if you still get the issue, let me know.
Hello,
I am trying to set up a build environment for an ESP32-S3 project, but I was having some warnings.
I managed to reproduce these warnings directly in
nixpkgs-esp-dev
by calling:I get the following output:
Would you happen to know what is causing this warnings?
During build, these warnings look slightly different:
Running
install.sh
downloads some packages to the user home directory and fails because it requirespip
. Shouldn't the install script be run as part of thenixpkgs-esp-dev
build?