ESP v5.0 removed mdns Why? (IDFGH-9213)
ESP v5.0 removed mdns Why? (IDFGH-9213)
In v4.4.3 we had mdns which I was using.
Upgraded to v5.0 and its gone.
Why did they remove it from the components folder, and examples ?
Upgraded to v5.0 and its gone.
Why did they remove it from the components folder, and examples ?
- ESP_Roland
- Posts: 265
- Joined: Tue Oct 09, 2018 10:28 am
Re: ESP v5.0 removed mdns Why?
mdns was moved into the component registry: https://docs.espressif.com/projects/esp ... nents.html, https://components.espressif.com/compon ... essif/mdns
Here is an example how you add it to your project: https://github.com/espressif/esp-idf/bl ... ent.yml#L2
Here is an example how you add it to your project: https://github.com/espressif/esp-idf/bl ... ent.yml#L2
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
Thanks for responding.
Out of curiosity, Why would you guys move it to the component registry?
Out of curiosity, Why would you guys move it to the component registry?
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
I'm not sure why it was moved. The documentation doesn't say. It tripped me up when I first changed to V5.0 from V4.4 as it wasn't noted in the 4.4 to 5.0 migration documentation.
You don't need to manually edit the yml component configuration file. The documentation for the component gives you the command to use to add the component. Once you do that, it should build just as it did before.
You don't need to manually edit the yml component configuration file. The documentation for the component gives you the command to use to add the component. Once you do that, it should build just as it did before.
Code: Select all
idf.py add-dependency "espressif/mdns^1.0.7"
-
- Posts: 9730
- Joined: Thu Nov 26, 2015 4:08 am
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
Generally, we're moving things to the component registry because it allows us to decouple the code from ESP-IDF releases. It means those components and ESP-IDF can be developed and released individually, meaning that a release of either doesn't have to wait until issues in the other are resolved.
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
Thank you both for the info!
Now I just need to figure out how to do it in PlatformIO. as we dont have idf.py ;-(
Now I just need to figure out how to do it in PlatformIO. as we dont have idf.py ;-(
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
Makes sense!ESP_Sprite wrote: ↑Fri Jan 27, 2023 1:37 amGenerally, we're moving things to the component registry because it allows us to decouple the code from ESP-IDF releases. It means those components and ESP-IDF can be developed and released individually, meaning that a release of either doesn't have to wait until issues in the other are resolved.
Assuming PlatformIO uses ESP-IDF (and I assume it does, otherwise we wouldn't be having this discussion ) then I think you just need to create by hand the yml file that ESP_Roland showed in his link. The `idf.py add-dependency` command just creates it for you.
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
Just wanted to update this for the solution incase anyone else needs to know how to do it for PlatformIO
At the root level of your project create a components folder and inside there create a mdns folder.
Then go here: https://components.espressif.com/compon ... essif/mdns
And click "download archive". Extract the contents into your components/mdns folder.
Open the root level CMakeLists.txt file (not the one in your src folder) and add "list(APPEND EXTRA_COMPONENT_DIRS)".
So it should now look simular to this (though your project(mdnsS3) will be the name of your project instead).
At the root level of your project create a components folder and inside there create a mdns folder.
Then go here: https://components.espressif.com/compon ... essif/mdns
And click "download archive". Extract the contents into your components/mdns folder.
Open the root level CMakeLists.txt file (not the one in your src folder) and add "list(APPEND EXTRA_COMPONENT_DIRS)".
So it should now look simular to this (though your project(mdnsS3) will be the name of your project instead).
Then clean & rebuild the project.cmake_minimum_required(VERSION 3.16.0)
include($ENV{IDF_PATH}/tools/cmake/project.cmake)
list(APPEND EXTRA_COMPONENT_DIRS)
project(mdnsS3)
Last edited by username on Sun Jan 29, 2023 2:51 pm, edited 1 time in total.
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
I don't think all that manual setup is necessary. The build process creates the components subfolder. You just need to run the `idf.py add-dependency` tool and it creates the necessary yml in your source folder. The build process takes care of the rest. (A full clean beforehand is recommended.)
Re: ESP v5.0 removed mdns Why? (IDFGH-9213)
Sorry, I will edit my previous post. That explanation was for doing it in platformIO.I don't think all that manual setup is necessary. The build process creates the components subfolder. You just need to run the `idf.py add-dependency` tool and it creates the necessary yml in your source folder. The build process takes care of the rest. (A full clean beforehand is recommended.)
Who is online
Users browsing this forum: Baidu [Spider] and 125 guests