Baby steps. Yes, the next thought is to implement a "basic" test using network connectivity. OK. Maybe not so many baby steps. I spent some time with it; I have RTP working; P2P and Multicast between macOS, Linux and ESP32/FreeRTOS. Basic session authentication seems to work. Next is to start activ...

So, I guess the next logical step would be to add a socket and have this library attempt to interpret an audio stream? Baby steps. Yes, the next thought is to implement a "basic" test using network connectivity. I will throw the warning down up front. This very well could be for nothing. This libra...

Not carefully enough...mea culpa. I went ahead and copied the library under your project structure (I'm running on Windows and links/shortcuts don't always do what I want them to). It now builds and runs. Very nice work on your part. No worries, first cup of coffee; I forgot the insert a smile. It ...

Was I supposed to copy the Cisco library into my local copy of your repo? I am guessing you didn't read any of the two (2) README files. :? My "repo" is an example project getting libsrtp built and used as a component. Yes, that example currently expects the libsrtp directory (or a symbolic link to...

Thank you for all you're doing on this. At some time, I'd appreciate seeing your work in more detail. I'm still quite new to CMake and its nuances. First Cut. I ended up taking a little more “brute force” approach using a “known good” config.h I had generated against the IDF toolchain separately. G...

Thank you for all you're doing on this. At some time, I'd appreciate seeing your work in more detail. I'm still quite new to CMake and its nuances. No worries, I decided to take it on as a pet "filler" project. I certainly don't need this library at the moment, but you never know when the need may ...

I do notice that my component seems to be based on a 2.n version of CMake. Is this going to present a problem for me? I took a quick look at the library. CMake aside, that is going to need some work to get setup for the esp-idf toolchain correctly. A configure for the xtensa-esp32-elf toolchain wen...

If I understand correctly, the term "library" as used in the ESP world doesn't refer to a pre-built .a file, but rather a collection of sources and build instructions. The term "library" or "component" does indeed refer to a pre-built .a (static library) file; pre-built in the context of building y...

I do notice that my component seems to be based on a 2.n version of CMake. Is this going to present a problem for me? I took a quick look at the library. CMake aside, that is going to need some work to get setup for the esp-idf toolchain correctly. A configure for the xtensa-esp32-elf toolchain wen...

Thanks fasani, Correct; You went far further explaining it than I. Everything is a library/component in the IDF build framework; including the "application" and the various freeRTOS and IDF bits. What I was trying to point out is that a projects local components directory is ( usually ) the "path of...