This option should be used for any executables which are used only
for testing, or for generating other files and are consequently never
installed. By specifying this option, we are telling Libtool that
the executable it links will only ever be executed from where it is
built in the build tree. Libtool is usually able to considerably
speed up the link process for such executables.
For a long time the RTP payload type was hard-coded for outgoing
frames. The problem is that according to RFC 3551 only GSM FR has
a static payload type value (see table 4, value 3). For other
codecs the payload type may be negotiated between the both
sides dynamically (i.e. in range 96-127).
Let's allow a binary/API user to configure this manually.
The 'distcheck' rule performs all of the operations associated with
packaging a distribution and verifying that the distribution works.
There were several problems:
- libgsmhr/Makefile.am: 'patches' dir was not listed in EXTRA_DIST
- libgsmhr/Makefile.am: (dist)clean targets wan't defined properly
- tests/Makefile.am: 'ref-files' dir was not listed in EXTRA_DIST
- tests/testsuite.at: wrong path was used for io_sample.txt
The talloc_enable_null_tracking() actually allocates a new talloc
context, which makes both Valgrind and LeakSanitizer angry. This
context should be freed by the talloc_disable_null_tracking().
In the 'ecu/ecu_fr_test' we have a processing queue with Full Rate
decoder block, which depends on libgsm. If libgsm isn't available,
the test will fail. Let's enable this test conditionally.
In I06a21f60db01bfe1c2b838f93866fad1d53fdcd1 the Error Concealment
Unit API for FR codec was introduced. This change implements a
Note: at the moment, only Full Rate is supported by the ECU API.
As the libosmogapk actually relies on external libraries for
audio coding, we should enable / disable particular codec
tests depending on the build configuration.
This test group is intended to check the format / codec transcoding
capabilities of the library. The reference files are used to ensure
that encoding or decoding was successful.
The following formats are currently being tested:
This test is intended to check the RTP source / sink operability.
To do this, two processing queues are being allocated:
"generator": source/random -> sink/rtp
"checker": source/rtp -> sink/checker
The first one generates some amount of random bytes (payload),
and stores them inside a buffer that is shared between both
After generation, a payload is being sent from the first
queue via an RTP sink, and then being received by the second
via an RTP source.
As both queues do use a shared buffer, the last item of the
second queue (named 'sink/checker') is able to compare a
received payload with expected.
This test is intended to check the file source / sink
operability. To do that, the following processing chain
is being composed:
source/file -> proc/dummy -> sink/file (stdout)
The source item opens the sample file named 'io_sample.txt'
for reading. The next processing item simply converts all
uppercase latters to the lowercase. The last one writes
the result to stdout.
This processing cycle is being repeated several times
with different block length values.
This test is intended to validate the processing queue
management API. Moreover, the talloc debugging API is
used to ensure that there are no memory leaks.
First, four processing queues are being allocated. One
of them is empty, while others have different count of
items. Then the human-readable description is being
generated for all of them. And finally, the processing
and exit cllback are being tested.
During the test execution, the talloc NULL-context
tracking feature is enabled, allowing to observe every
memory allocation within the libosmogapk, and to detect