You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Addition of a received application ACK notification callback
* Lifecycle management improvements
* Exposed failure on progressive back-off/retry logic
* Hardening/fixing various edge-cases
Copy file name to clipboardExpand all lines: README.md
+36-15Lines changed: 36 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,22 @@ Amazon Kinesis Video Streams Producer SDK for C/C++ contains the following sub-d
17
17
* kinesis-video-native-build - Native build directory with a build script for Mac OS/Linux/Raspberry PI. This is the directory that will contain the artifacts after the build.
18
18
19
19
## Building from Source
20
+
There are few build-time tools/dependencies which need to be installed in order to build the core SDK libraries and the samples.
21
+
22
+
### Build Dependencies
23
+
Please install the following additional build tools before proceeding (the example below is for Mac Os X).
24
+
* autoconf 2.69 (License GPLv3+/Autoconf: GNU GPL version 3 or later) http://www.gnu.org/software/autoconf/autoconf.html
After you've downloaded the code from GitHub, you can build it on Mac OS or Ubuntu using ./kinesis-video-native-build/install-script script. This will produce the core library, the JNI library, unit tests executable and the sample GStreamer application. The script will download and build the dependent open source components in the 'downloads' directory and link against it.
21
34
22
-
Important: Set the JAVA_HOME environment variable to your version of the JDK `export JAVA_HOME=<your java home directory>` in order to build and link JNI component.
35
+
**Important:** Set the JAVA_HOME environment variable to your version of the JDK `export JAVA_HOME=<your java home directory>` in order to build and link JNI component.
23
36
24
37
The bulk of the install script is building the open source dependencies. The project is based on CMake so the open source components building can be skipped if the system versions can be used for linking. Running 'cmake . && make' from the kinesis-video-native-build directory will build and link the SDK.
25
38
@@ -45,16 +58,6 @@ The projects depend on the following open source components. Running `install-sc
Kinesis Video Streams Produicer SDK for C++ needs to establish trust with the backend service through TLS. This is done through validating the CAs in the public certificate store. On Linux-based models, this store is located in /etc/ssl/ directory by default.
60
63
@@ -216,11 +219,29 @@ OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
216
219
217
220
* Raspberry PI failure to load the camera device. To check this is the case run `ls /dev/video*` - it should be file not found. The remedy is to run the following:
218
221
219
-
> vcgencmd get_camera
220
-
supported=1 detected=1
222
+
$ls /dev/video* {not found}
223
+
224
+
$vcgencmd get_camera {output is similar to supported=1 detected=1}
225
+
226
+
if the driver does not detect the camera then
227
+
228
+
* Check for the camera setup and whether it's connected properly
229
+
* Run firmware update `$ sudo rpi-update` and restart
230
+
231
+
$sudo modprobe bcm2835-v4l2
232
+
233
+
$ls /dev/video* {lists the device}
234
+
235
+
236
+
* Raspberry PI timestamp/range assertion at runtime. Update the Raspberry PI firmware.
237
+
238
+
$ sudo rpi-update
239
+
240
+
$ sudo reboot
241
+
242
+
243
+
* Raspberry PI GStreamer assertion on gst_value_set_fraction_range_full: assertion 'gst_util_fraction_compare (numerator_start, denominator_start, numerator_end, denominator_end) < 0' failed. The uv4l service running in the background. Kill the service and restart the sample app.
221
244
222
-
> sudo modprobe bcm2835-v4l2
223
-
> ls /dev/video*
224
245
225
246
* Raspberry PI seg fauls after some time running on libx264.so. Rebuilding the libx264.so library and re-linking the demo application fixes the issue.
0 commit comments