Deploying the Server Debugging Environment
- Save the VideoEngine.tar.gz package to the /home/VideoEngine/Cloud directory.
- Decompress the development package of the video stream engine server.
tar xzvf VideoEngine.tar.gz
- Copy the extracted binary files to a cloud phone (for example, cloudphone_1).
docker cp system/bin cloudphone_1:/system/ docker cp system/etc cloudphone_1:/system/ docker cp system/lib cloudphone_1:/system/ docker cp system/lib64 cloudphone_1:/system/ docker cp vendor/lib cloudphone_1:/vendor/ docker cp vendor/lib64 cloudphone_1:/vendor/ docker cp vendor/etc cloudphone_1:/vendor/
- Copy the external dependency libraries of the video stream cloud phone to a cloud phone (cloudphone_1 for example). Table 1 lists the required dependency libraries.
Table 1 External dependency libraries of the video stream cloud phone Item
Library Name
Paths
Encoding dependency library
libVideoCodec.so
/vendor/lib, /vendor/lib64
Decoding dependency library
libVideoDecoder.so
/vendor/lib, /vendor/lib64
GPU acceleration dependency library
libVmiEncTurbo.so
/vendor/lib, /vendor/lib64
GPU acceleration dependency library (system permission)
libVmiEncTurboSys.so
/system/lib, /system/lib64
Opus encoding and decoding library
libVmiOpus.so
/system/lib, /system/lib64
- Restart the cloud phone, and then the video stream cloud phone can run. You can debug the functions by calling the corresponding APIs according to the subsequent development process.
Parent topic: Configuring the Development Environment