Yes, the licensing of the ST library is part of the problem. In the long run it would be good to move away from that.
I have used the OpenCM3 library for basic stuff, but not DSP. Don On Tue, Jun 26, 2018 at 01:55:14PM -0500, Steve wrote: > There was an earlier discussion. The problem is, the library is not > open source. It is free of royalty, but you now have to register to > download it. Thus, the theory is, that anyone who wants to create an > STM product, should use the STM software after registering, and as far > as I read, they don't allow publishing their library. > > By the way, the library is now deprecated, as they have a new system. > However, Codec2 is no where near compatible with the new library. > > I also believe the Makefile is now obsolete, and we should be using > the cmake build. I have not gone with that in my testing, but I will > have to port the Makefile to cmake when the code matures, and the > sm700d is merged. > > Steve > > On Tue, Jun 26, 2018 at 12:53 PM Don <don_li...@db-reid.com> wrote: > > > > The stm32/Makefile has rules to download and extract the ST provided > > library for STM32F4. The location specified > > > > http://www.st.com/resource/en/firmware/stm32f4_dsp_stdperiph_lib.zip > > > > does not work for me. However it was easy to find the file and get it. > > Now I have to have a hacked Makefile that comments this stuff out. That > > makes it awkward to make other changes and get them checked in. > > > > Downloading this library is a one-time thing when you start working on > > this code. In fact I don't think you want to get a new version if it > > ever appears unless you are ready for it. So this does not need to be > > in the Makefile. > > > > What I'd like to do is to put instructions for downloading the library > > into the README file and take this part out of the Makefile. I'll also > > have the Makefile use an ENV value for the location if set, otherwise > > use the default location from the README. > > > > Does that work for people?? > > > > Don Reid > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Freetel-codec2 mailing list > > Freetel-codec2@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freetel-codec2 mailing list > Freetel-codec2@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
