Revision history [back]

You will need to backup the following:

• Any source code changes you made. (If your changes are already pushed to another github repo, that's fine.)
• The dynamic libraries (.so, .dll) and/or static libraries (.a, .lib), among others. Basically, any final products from the build.
• Debug symbols or any other files needed to troubleshoot a problem that exist inside OpenCV code

When backing up the compiled library files, you will need a thorough understanding of everything that needs to be backed up. This means second-level, third-level, etc, dependencies; all must be backed up.

Check each of the OpenCV "modules" you use.

Check each of the OpenCV "3rdparty" modules as well.

In case you move the locations of static or dynamic libraries after building, you may need to modify the hard-coded links that are embedded into your application, using a tool called chrpath. See documentations

You will need to backup the following:

• Any source code changes you made. (If your changes are already pushed to another github repo, that's fine.)
• The dynamic libraries (.so, .dll) and/or static libraries (.a, .lib), among others. Basically, any final products from the build.
• Debug symbols or any other files needed to troubleshoot a problem that exist inside OpenCV code

To write C++ programs that can call into OpenCV API, you need the OpenCV include headers too.

When backing up the compiled library files, you will need a thorough understanding of everything that needs to be backed up. This means second-level, third-level, etc, dependencies; all must be backed up.

Check each of the OpenCV "modules" you use.

Check each of the OpenCV "3rdparty" modules as well.

In case you move the locations of static or dynamic libraries after building, you may need to modify the hard-coded links that are embedded into your application, using a tool called chrpath. See documentations