I've taken the code base and refactored it to be able to built with Autotools. This adds "./configure" support, so that the code can be easily ported to different platforms, without require extensive Makefile knowledge and edits.
Also added better checks for required headers/packages/libraries.
Lots of variable substitution in scripts to properly reference the location of the config files, (they should be found wherever they get configured/installed, instead of hard coded looking in /etc/rmsgw).
Removed some obsolete/unused files.
One big departure from the standard deployment is that this code currently installs and runs as root, instead of rmsgw/rmsgw. Is that really a big deal? Support for that could probably be added with some hooks, but I question how big of a security risk it would be, considering this software is primarily accessed over radio...
Next step will be to add support for building a Debian package, that shouldn't be too hard now.
I've taken the code base and refactored it to be able to built with Autotools. This adds "./configure" support, so that the code can be easily ported to different platforms, without require extensive Makefile knowledge and edits.
Also added better checks for required headers/packages/libraries.
Lots of variable substitution in scripts to properly reference the location of the config files, (they should be found wherever they get configured/installed, instead of hard coded looking in /etc/rmsgw).
Removed some obsolete/unused files.
One big departure from the standard deployment is that this code currently installs and runs as root, instead of rmsgw/rmsgw. Is that really a big deal? Support for that could probably be added with some hooks, but I question how big of a security risk it would be, considering this software is primarily accessed over radio...
Next step will be to add support for building a Debian package, that shouldn't be too hard now.