Closed SinglWolf closed 2 years ago
Could you maybe check in the esp-sr repository for issue?All errors seem to be there.
Could you maybe check in the esp-sr repository for issue?All errors seem to be there.
In the repository https://github.com/espressif/esp-sr/tree/master/include
there is no directory for esp32s2
.
Only esp32
and esp32s3
.
It is using the esp32
directory for S2, which is fine. See here. Issue must be elsewhere in that repository.
It is using the
esp32
directory for S2, which is fine. See here. Issue must be elsewhere in that repository.
I'm sorry, of course, but why should a simple user look for and fix a developer's problem???
I'm not asking you to fix it, but rather to report it there. The problem you are having is not in the lib-builder and it is an external component to this project.
The problem you are having is not in the lib-builder and it is an external component to this project. I'm not asking you to fix it, but rather to report it there.
"The sheriff is not interested in the problems of the Indians"? People buy a car of a popular model. Everything was fine and suddenly the new cars started having engine problems. The owners turn to the car manufacturer with a claim. In response, they receive this: "We do not manufacture engines for this car. Make claims to the manufacturer of these engines." Funny, but very relevant. I went the other way. I just replaced the component code from the archive of the release version and the compilation was successful.
so you expect the sales team to know why your crankshaft failed? Unless it's a known problem, they can only send you to the service to have it checked, but even if it's known, it's still work for the car service, not for the sales team. Good on you for replacing the engine with older model, without letting the service know that there is a problem :)
Master branch. The command
./build.sh -t esp32s2
causes an error: