[Ovmsdev] ESP-IDF v4 / v5 - baby steps
ll-ovmsdev at lange.nom.fr
Mon Mar 6 04:05:06 HKT 2023
No I did not have this issue yet - as I'm still on v5.0.1
If it were me, I'd recommend that you use 'tag' names (
https://github.com/espressif/esp-idf/tags ) instead of branch names
(https://github.com/espressif/esp-idf/branches ) as it seems they are
somehow in a state of flux on branch `release/v5.0`.
The docker image has all the branches and tags available, and among
those is the `v5.0.1` tag:
So instead of pulling `espressif/idf:release-v5.0` it would be
`espressif/idf:v5.0.1` and it "should work".
I'll have a look at the next v5 when it's tagged - may be they will
document a deprecation or a change in includes.... we'll see.
If you really really want that we investigate this (moving)
`release/v5.0` branch, let me know, and I'll try to have a look at it.
Le 04/03/2023 à 14:04, Michael Balzer a écrit :
> I was about to review & test your latest changes, but unfortunately
> did an update of the release-v5.0 docker image and am now experiencing
> the missing mbedtls module issue again :-/
> undefined reference to `mbedtls_pkcs5_pbkdf2_hmac'
> esp-idf/zip/libzip.a(zip_crypto_mbedtls.c.obj): in function
> /project/components/zip/libzip/lib/zip_crypto_mbedtls.c:124: undefined
> reference to `mbedtls_pkcs5_pbkdf2_hmac'
> Did you have this, if so did you find a solution?
> Am 18.02.23 um 10:12 schrieb Michael Balzer:
>> The build works using the same sdkconfig with
>> "espressif/idf:release-v5.0" (and again fails at that mbedtls module
>> when switching back to the "latest" image).
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev