-
Notifications
You must be signed in to change notification settings - Fork 135
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
error: failed to run custom build command for esp-idf-sys v0.33.2
#248
Comments
This is a debian specific problem. You can't rawly install python packages via pip if its not in a venv or through apt, they enforced this now in debian 12. The esp-idf installtation try's to install virtualenv if its not found, but this failed because its only allowed inside a virtualenv. But because the virtualenv is not created you got this error. |
Hi @Vollbrecht, did the following: $ sudo apt-get install python3-virtualenv
|
did you install via espup ? make sure your env variables are not poluted and that you source the export script |
$ espup install .... |
thats not how you source env file on debian - please also check out esp-rs/esp-idf-hal#319 for more info regarding this specific problem |
thanks - will check tomorrow |
Yeah, to cut some chasing in the (long) other thread @Vollbrecht mentioned, you need to do, exactly: And I'm so sick and tired of this problem :( |
@SergioGasquez Enjoy your vacation, but maybe another nail on the "export" script coffin. :) |
$ . ~/export-esp.sh Compiling esp-idf-svc v0.46.2 thanks a lot to @ALL !
Sorry about that! |
Hi,
using Debian 12 on x86_64
did following:
$ rustup toolchain install nightly --component rust-src
$ cargo install cargo-generate
$ cargo install ldproxy
$ cargo install espflash
$ cargo install cargo-espflash
$ rustc --version
rustc 1.73.0-nightly (9163a2087 2023-10-03) (1.73.0.0)
$ cargo generate --git https://github.com/esp-rs/esp-idf-template cargo
$ cargo build
How can I fix this ?
I tyed this:
$ cargo add virtualenv-rs
but got this by running: cargo build
The text was updated successfully, but these errors were encountered: