The default remains the same: we show the huge ClueCon nag banner on
startup and in fs_cli.
However, if you pass --disable-huge-cluecon-nag, no banner will be
shown.
If you pass --enable-modest-cluecon-nag, a modest text-based ClueCon
reminder will be shown instead.
Enhancements to trace logging, include threads and context ID.
Changed default opal_conf.xml to allow more than just G.711 uLaw and not to clutter log file with debug logs.
Added to opal_conf.xml item for "disable-transcoding".
Updated build/buildopal.sh to use correct ./configure items for PTLib, allow for something other than standard install directory for PTLib/OPAL and be able to easily bind to a specific release of PTLib/OPAL.
Our main version string is designed for release engineering purposes:
it matches file name conventions used for versioned tarballs and the
versions sort lexicographically while containing all pertinent
information.
With this commit we add in parentheses a more human-friendly rendering
of the version string: we spell out the meaning of each field and
render the datetime in RFC 822 notation.
Showing whether the git repository is clean at the time of build will
be useful, but currently something in our bootstrap/configure/early
make process is causing the tree to look unclean at just the wrong
moment and clean builds are showing up as unclean.
This amends commit f8be71ac6df5dc17a9bb67662c59b01da7a46884.
This still should resolve FS-4303.
What's going on here is that we need a portable way to access
strftime. date(1posix) doesn't provide enough. And without perl, I
can't think of a better way to get to it than just using C. So the
logic for generating the extended revision has been moved into a small
self-contained and hopefully portable C program.
Our default build probably shouldn't include non-free software. With
mod_ilbc, the licensing situation is merely ambiguous. With
mod_siren, the user can't use this code without getting explicit
permission from Polycom (though it is apparently easily given).
