I have moved this discussion to [email protected], as
digitalvoice is supposed to be a user list. Richard, please subscribe at
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
if you have not already done so.
On 4/11/2013 7:24 AM, Richard wrote:
One thing I've run into is that the autoconf/automake configuration
needs some significant tweaking in some cases and to be honest, I'm
not very good with it, so my "fixes" have been very much hacks.
I congratulate you on your politeness in speaking of autoconf/automake.
I personally could not describe it sufficiently without, I suspect,
first learning how to swear in Arabic. It's definitely time to move on
to something else.
I'm *more* comfortable in the cmake arena although I'm no expert.
That's fine. If you would jump right in and try to make it work
side-by-side with the present stuff so that autoconf/automake does not
break, that would greatly facilitate cutting over. You might have to use
alternate names for Makefiles and invoke them with "make -f". But it
seems to me that this could be done.
Some questions/suggestions for Codec2:
There are some VERY generic names for the headers (sine.h, fft,h, etc)
which could very likely conflict with existing linux packages so for
my RPM I moved them into /usr/include/cocdec2/. Theoretically I could
have left codec2.h in /usr/include but from a hack perspective it was
easier to move all of them.
Yes, it is simply good engineering to put these in a codec2 directory
/if they are installed at all./
Also, there seems to be a need for more tweaking on exactly what
headers get installed...
It might be that some of this code is shared between our modems, codec,
and freedv, but they shouldn't be exposed outside of the project's own
compilation directories. One should only need to place headers that
define external APIs under /usr/include .
FreeDV:
Although not required, it's generally preferred to name the package
the same as the source archive, but fdmdv doesn't exactly roll off
the tongue...
FDMDV is the name of someone else's application from which we cribbed
the modem design and perhaps some UI elements, but nothing copyrighted.
Actually, we use it more for the HF modem today than the application. We
can change that sometime, probably with a major version change.
I've begun work on creating a cmake configuration starting with
configure.ac and got a lot of the library detection working and
checking for headers. My next step is to re-implement the function checks.
The real trick is getting it to work on Linux (.rpm|.deb), *BSD,
Windows, MacOS, and (libraries only) cross-compile to Android. This is a
good reason that present stuff should be left standing alongside for a
while.
I guess my question to the group is: Is there any interest in
supporting a cmake based build?
Very much so. The only reason it's not being done is that the other
developers are having life get in the way. If you can put in the time
we'd be very appreciative.
Thanks
Bruce
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
