-
Notifications
You must be signed in to change notification settings - Fork 125
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
Using esp-idf-sys without downloading anything #132
Comments
Yes, this is possible, and its what I use daily :). esp-idf is a hard dependency on esp-idf-sys so the options are have it downloaded already or download it, the latter being the default for ease of use. If you download esp-idf manually, run the tool install script once, then all you have to do is source the idf environment (steps 3-5 from here). Once the environment is sourced, esp-idf-sys will use those sources to build esp-idf, instead of downloading it.
|
Sadly this still errors, albeit with a different error:
and the content of that file
This doesn't seem to come from |
I made a |
Did you anything like this? When I try it with my repository I get following:
|
closing in favor of #184 |
I am a nixos user and would like to use
esp-idf-sys
. However, it insists on downloading things while building (imo a bad idea, it is very unexpected), which I cannot do.I am using the ESP32-C3 and do not want to use the xtensa toolchain, and instead just use the normal cargo compiler targeting riscv. Currently, this is not possible, as it requires either 'native' or 'pio'. Neither of which I want to use.
Is there any way I can still use your project?
Things that would be required for my usecase:
Thanks!
Edit
Looking more into it, it seems that the project is expecting a git repository. This seems unecessary when 'fromenv' is supplied? I expect the crate to assume that all the necessary tools/files are accessible in the PATH or in the env variables as if an
$ESP_IDF/export.*
was called.In my case for example, I can install ESP_IDF into my environment, but that does not come with any git information. (After all, why is that important? I am using fromenv after all.)
The text was updated successfully, but these errors were encountered: