Application Migration to DeepStream 7.0 from DeepStream 6.4
Running DeepStream 6.4 compiled Apps in DeepStream 7.0
To run the old app from DeepStream 6.4 in DeepStream 7.0, create symlinks of the libraries so the old application can find them.:
mkdir /opt/nvidia/deepstream/deepstream-6.4
mkdir /opt/nvidia/deepstream/deepstream-6.4/lib
ln -s /opt/nvidia/deepstream/deepstream-7.0/lib/* /opt/nvidia/deepstream/deepstream-6.4/lib/
Compiling DeepStream 6.4 Apps in DeepStream 7.0
Before compiling DeepStream 6.4 applications in DeepStream 7.0, modify the Makefiles and set the NVDS_VERSION flag to 7.0.
There are two options to compile DeepStream 6.4 in DeepStream 7.0:
Option 1: Replace existing
sources/appsfrom DeepStream-7.0 and copy the entire`sources/appsdirectory from DeepStream-6.4.Option 2 : Individual applications in DeepStream SDK have dependency on sources under
apps-commondirectory. Ideally, to compile those applications, you must use the same version of apps-common. In case you want to use the latest version, you may need to adjust some application function calls because of a change in application function definitions.
Migrating DeepStream 6.4 Gst-nvtracker to DeepStream 7.0
In DeepStream 7.0, the past-frame data structure of Gst-nvtracker is renamed as Target Miscellaneous Data in nvds_tracker_meta.h; and accordingly,
NvDsPastFrameObj, NvDsPastFrameObjList, NvDsPastFrameObjStream and NvDsPastFrameObjBatch are renamed as
NvDsTargetMiscDataFrame, NvDsTargetMiscDataObject, NvDsTargetMiscDataStream and NvDsTargetMiscDataBatch, respectively.
If a DeepStream 6.4 application or custom tracker uses the past-frame data, it should adopt the new miscellaneous data structures and recompile the source code when migrating to DS 7.0.
Note
By default, OpenCV is deprecated in DeepStream 6.1. However, you can enable OpenCV in plugins such as nvinfer (nvdsinfer) and dsexample (gst-dsexample) by setting WITH_OPENCV=1 in the Makefile of these components. Refer to the component README for more instructions.