Run and verify the code
To run and verify the code for the Use the C++ producer library, do the following:
- 
                Run the following commands to create a builddirectory in your downloaded C SDK, and launch cmakefrom it:mkdir -p amazon-kinesis-video-streams-producer-c/build; cd amazon-kinesis-video-streams-producer-c/build; cmake ..You can pass the following options to cmake ..- 
                        -DBUILD_DEPENDENCIES- whether to build depending libraries from source.
- 
            -DBUILD_TEST=TRUE- build unit and integration tests. Might be useful to confirm support for your device../tst/webrtc_client_test
- 
                        -DCODE_COVERAGE- enable coverage reporting.
- 
                        -DCOMPILER_WARNINGS- enable all compiler warnings.
- 
                        -DADDRESS_SANITIZER- build with AddressSanitizer.
- 
                        -DMEMORY_SANITIZER- build with MemorySanitizer.
- 
                        -DTHREAD_SANITIZER- build with ThreadSanitizer.
- 
                        -DUNDEFINED_BEHAVIOR_SANITIZER- build with UndefinedBehaviorSanitizer.
- 
                        -DALIGNED_MEMORY_MODEL- build for aligned memory model only devices. Default isOFF.
 
- 
                        
- 
                Navigate to the builddirectory that you just created with the previous step, and runmaketo build the WebRTC C SDK and its provided samples.make
- 
                The sample application kinesis_video_cproducer_video_only_samplesends h.264-encoded video frames inside the foldersamples/h264SampleFramesto Kinesis Video Streams. The following command sends the video frames in a loop for ten seconds to Kinesis Video Streams:./kinesis_video_cproducer_video_only_sample YourStreamName 10If you want to send H.264-encoded frames from another folder (for example, MyH264FramesFolder), run the sample with the following arguments:./kinesis_video_cproducer_video_only_sample YourStreamName 10 MyH264FramesFolder
- 
                To enable verbose logs, define the HEAP_DEBUGandLOG_STREAMINGC-defines by uncommenting the appropriate lines inCMakeList.txt.
You can monitor the progress of the test suite in the debug output in your IDE. You
            can also monitor the traffic on your stream by watching the metrics that are associated
            with your stream in the Amazon CloudWatch console, such as
            PutMedia.IncomingBytes.
Note
The console doesn't display the data as a video stream because the test harness only sends frames of empty bytes.