Hi Richard,

I am starting my coding pass, with a few bug fixes on FreeDV and the coding of the GUI-less front-end. After a little pain understanding how to use it (I'm still a cmake newbie), cmake comes right up and the software builds to completion without a problem on my Debian system. Which is a tremendous relief compared to what we used to have. Thanks very much for your work on that.

Please add this to your README: Don't ever run cmake in the source directory! Everything breaks in your build directory with not-well-directed error messages until you flush the files that it made.

Maybe the CMakeList commands should check for that. If cmake is run and ./CMakeLists.txt exists, print a message about the need to create a build directory and run it from there, and stop.

It would also be useful for the various platform build folks to collect the set of commands necessary to set up the environment for CMake on clean installs of their platforms, and leave them in files that can be run as scripts. On Debian/Mint/Ubuntu, a "SETUP_ENVIRONMENT.sh" script would look like:

    apt-get install cmake gcc g++ make svn ...

Again, thanks very much for this work.

    Bruce
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to